linux-kernel - Re: x2apic boot failure on recent sandy bridge system

lists.openwall.net		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]

Message-ID: <1323735902.1984.165.camel@sbsiddha-desk.sc.intel.com>
Date:	Mon, 12 Dec 2011 16:25:02 -0800
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	"Berck E. Nash" <flyboy@...il.com>
Cc:	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: x2apic boot failure on recent sandy bridge system

On Mon, 2011-12-12 at 15:21 -0800, Berck E. Nash wrote:
> On 12/11/2011 08:40 PM, Yinghai Lu wrote:
> > x2apic pre-enabled skip the mapping for lapic address. so need map it
> > after fall back.
> > 
> > please check attached -v5..
> 
> It appears to work correctly as far as I can tell.

Ok. In this case, it looks like bios didn't enable interrupt-remapping
(part of vt-d) and just enabled x2apic with out touching or exporting
vt-d HW.

Yinghai, In other scenarios where OS can't recover, mostly likely we
will fail in check_timer() when we fall back to xapic. Can we add a
printk in this case to convey the potential reason (that I mentioned in
the previous e-mail), so that the user can get more accurate information
for the check timer failure.

thanks,
suresh

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/