Date: Thu, 13 Jan 2022 17:29:21 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com> Cc: xen@freebsd.org Subject: Re: VCPUOP_send_nmi returns -38 Message-ID: <7fb3c0fe-0145-7474-aa5e-0ad2dbb17e9e@FreeBSD.org> In-Reply-To: <YeA9wDPWQ%2BAJH1aN@Air-de-Roger> References: <3f9f173b-40b9-0180-404d-52fa56dde45f@FreeBSD.org> <a27fb9ea-1078-fbbd-3dd9-9ce60de08c22@FreeBSD.org> <Yd1bR6mSAjL6VMYD@Air-de-Roger> <787faaf6-c639-0f6a-1a16-c4fb7a5506e5@FreeBSD.org> <YeA9wDPWQ%2BAJH1aN@Air-de-Roger>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/01/2022 16:57, Roger Pau Monné wrote: > I've got two patches for you to try, the first one is 'mni-fix.patch' > and should fix the NMI sending issue. > > I'm also attaching a second patch, that should allow your guest to use > x2APIC. FreeBSD has previously prevented Xen guests from using x2APIC > because of a bug in old Xen versions, but I think this should be > solved now, so if FreeBSD can successfully boot on your VM with the > patch applied I think we are safe to enable x2APIC. That one is called > 'x2apic.patch'. > > Let me know how the testing goes. Tested both patches, both jointly and independently. x2APIC mode gets successfully enabled: # sysctl hw.apic hw.apic.timer_tsc_deadline: 0 hw.apic.eoi_suppression: 0 hw.apic.x2apic_mode: 1 hw.apic.enable_extint: 0 Not seeing any obvious regressions when running with it. NMIs are successfully sent and delivered now as well. Thank you very much! -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7fb3c0fe-0145-7474-aa5e-0ad2dbb17e9e>