lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 20 Dec 2012 08:46:59 -0800
From:	Yinghai Lu <>
To:	"Zhang, Lin-Bao (Linux Kernel R&D)" <>
Cc:	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>, "" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: Why Linux kernel forced to enter X2APIC mode( just because of
 booting cpu has supported x2apic) without depending on BIOS' setting in
 MSR->x2apic enablement bit ?

On Thu, Dec 20, 2012 at 2:38 AM, Zhang, Lin-Bao (Linux Kernel R&D)
<> wrote:
> I think current core argument is our BIOS did following judgement ,
> but Linux kernel did not(Linux seems just judge BSP supports x2apic mode or not by CPUID method)

kernel checks that, if the BSP in x2apic mode, kernel will check if
intr-remapping can be enabled, otherwise
it will switch back to xapic mode.

> Our BSP really supports x2apic mode, however,as this spec, our BIOS think some of configuration of server
> could not meet x2apic conditions ,So didn't place local xAPICs into x2apic mode.
> But linux kernel indeed enable x2apic mode(just believe BSP, didn't do above judgement) . so this is the conflict.

so your BIOS is wrong,  it does not enable intr-remapping.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists