linux-kernel - Re: [PATCH] x86,APIC: Detect lapic_is_integrated() once

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: <4A171224.5090500@zytor.com>
Date:	Fri, 22 May 2009 13:59:16 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
CC:	Rakib Mullick <rakib.mullick@...il.com>,
	Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Yinghai Lu <yhlu.kernel@...il.com>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>
Subject: Re: [PATCH] x86,APIC: Detect lapic_is_integrated() once - use on
 and on.

Cyrill Gorcunov wrote:
> [H. Peter Anvin - Fri, May 22, 2009 at 01:23:53PM -0700]
> | Cyrill Gorcunov wrote:
> | > 
> | > It was about a half year ago (need googling to be precise :)
> | > but I was reported about Xeon processor which identify itself
> | > as having "external" apic. So I hardly believe if real external
> | > device with ICC bus were used.
> | >  
> | 
> | Details, please.  It might even be a bug in the test.
> | 
> | 	-hpa
> | 
> 
> Here is it
> 
> 	http://lkml.org/lkml/2008/10/17/147
> 	http://lkml.org/lkml/2008/10/20/144
> 
> and commit db96b0a in mainline
> 

There isn't much detail about the system... no cpuinfo nor any DMI
information.  This makes me believe that the problem was misdiagnosed,
as you yourself speculate at the end of the thread.

It's also possible that this particular Xeon might have a different kind
of APIC, but if so, that's not the same thing as this being a
non-integrated APIC.  Unfortunately Xeon just means "Intel server chip"
and without a CPUID it's impossible to know what CPU that was.

	-hpa
--
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/