Date: Tue, 6 Sep 2016 17:08:28 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: Andriy Gapon <avg@FreeBSD.org>, stable@FreeBSD.org Subject: Re: X2APIC support Message-ID: <20160906140828.GD38409@kib.kiev.ua> In-Reply-To: <20160906131305.GI34394@zxy.spb.ru> References: <20151212130615.GE70867@zxy.spb.ru> <20151212133513.GL82577@kib.kiev.ua> <20160901112724.GX88122@zxy.spb.ru> <20160901114500.GJ83214@kib.kiev.ua> <20160901121300.GZ88122@zxy.spb.ru> <4ba05c00-f737-f562-553d-a7fa59145768@FreeBSD.org> <20160906131305.GI34394@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 06, 2016 at 04:13:05PM +0300, Slawa Olhovchenkov wrote: > On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote: > > > On 01/09/2016 15:13, Slawa Olhovchenkov wrote: > > > DMAR: Found table at 0x79b32798 > > > x2APIC available but disabled by DMAR table > > > > > Event timer "LAPIC" quality 600 > > > LAPIC: ipi_wait() us multiplier 1 (r 116268019 tsc 2200043851) > > > ACPI APIC Table: <ALASKA A M I > > > Is this significant? On carsh case present 'x2APIC available but > disabled by DMAR table' and 'LAPIC: ipi_wait() us multiplier 1 (r > 116268019 tsc 2200043851)' Significant for what ? First message mostly repeat the setting in the BIOS which you frobbed. The second message indicates that xAPIC timings for ICR reads were calibrated, i.e. x2APIC mode was indeed disabled. > > On successful boot both messages absent: > > Table 'DMAR' at 0x79b32798 > DMAR: Found table at 0x79b32798 > Event timer "LAPIC" quality 600 > ACPI APIC Table: <ALASKA A M I >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160906140828.GD38409>