From: "H. Peter Anvin" <hpa@zytor.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Rakib Mullick <rakib.mullick@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yhlu.kernel@gmail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] x86,APIC: Detect lapic_is_integrated() once - use on and on.
Date: Fri, 22 May 2009 13:59:16 -0700 [thread overview]
Message-ID: <4A171224.5090500@zytor.com> (raw)
In-Reply-To: <20090522203529.GI5354@lenovo>
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
next prev parent reply other threads:[~2009-05-22 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 13:31 [PATCH] x86,APIC: Detect lapic_is_integrated() once - use on and on Rakib Mullick
2009-05-22 20:02 ` Cyrill Gorcunov
2009-05-22 20:12 ` H. Peter Anvin
2009-05-22 20:21 ` Cyrill Gorcunov
2009-05-22 20:23 ` H. Peter Anvin
2009-05-22 20:30 ` Cyrill Gorcunov
2009-05-22 20:35 ` Cyrill Gorcunov
2009-05-22 20:59 ` H. Peter Anvin [this message]
2009-05-22 22:18 ` Maciej W. Rozycki
2009-05-23 13:07 ` Cyrill Gorcunov
2009-05-22 20:33 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A171224.5090500@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=rakib.mullick@gmail.com \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox