From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Suresh Siddha" <suresh.b.siddha@intel.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Jack Steiner" <steiner@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: add apic probe for genapic 64bit v2
Date: Tue, 22 Jul 2008 11:40:13 -0700 [thread overview]
Message-ID: <86802c440807221140o20dcc31fjc10f86a22a1125bb@mail.gmail.com> (raw)
In-Reply-To: <20080722181056.GD14380@linux-os.sc.intel.com>
On Tue, Jul 22, 2008 at 11:10 AM, Suresh Siddha
<suresh.b.siddha@intel.com> wrote:
> On Tue, Jul 22, 2008 at 11:05:17AM -0700, Yinghai Lu wrote:
>> On Tue, Jul 22, 2008 at 10:57 AM, Suresh Siddha
>> <suresh.b.siddha@intel.com> wrote:
>> > Yinghai, though not directly realted to this probe cleanup, what is this
>> > 'max_physical_apicid' doing.
>> >
>> > I don't understand the need for this commit.
>> >
>> >> commit e0da33646826b66ef933d47ea2fb7a693fd849bf
>> >> Author: Yinghai Lu <yhlu.kernel@gmail.com>
>> >> Date: Sun Jun 8 18:29:22 2008 -0700
>> >>
>> >> x86: introduce max_physical_apicid for bigsmp switching
>> >>
>> >> a multi-socket test-system with 3 or 4 ioapics, when 4 dualcore cpus or
>> >> 2 quadcore cpus installed, needs to switch to bigsmp or physflat.
>> >>
>> >> CPU apic id is [4,11] instead of [0,7], and we need to check max apic
>> >> id instead of cpu numbers.
>> >
>> > for logical flat, it really shouldn't matter how large the physical apic id
>> > is. In logical flat, OS programs the LDR and the limitation is the
>> > number of cpu's which is '8'.
>>
>> before i clean up 32bit, 64bit already used max_physical_apicid to
>> check if need to switch to physflat.
>
> No. It was introduced by your commit e0da33646826b66ef933d47ea2fb7a693fd849bf
>
> we were using num_possible_cpus > 8 check before.
yes. 64bit is changed to use max_phys_apicid at same patch
>
>> for 32bit, if not switch to bigsmp, cpu with physical apic id >=8 can
>> not be started by BSP.
>
> why?
could be apic mode is set to phys flat mode by BIOS.
get
APIC error (0x40)...
that is the reason for introducing max_phys_apicid.
next prev parent reply other threads:[~2008-07-22 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 1:36 [PATCH] x86: add apic probe for genapic 64bit Yinghai Lu
2008-07-22 5:08 ` [PATCH] x86: add apic probe for genapic 64bit v2 Yinghai Lu
2008-07-22 7:07 ` Ingo Molnar
2008-07-22 7:13 ` Ingo Molnar
2008-07-22 8:09 ` Yinghai Lu
2008-07-22 8:24 ` Ingo Molnar
2008-07-22 8:26 ` Yinghai Lu
2008-07-22 16:31 ` Mike Travis
2008-07-22 17:57 ` Suresh Siddha
2008-07-22 18:05 ` Yinghai Lu
2008-07-22 18:10 ` Suresh Siddha
2008-07-22 18:40 ` Yinghai Lu [this message]
2008-07-22 19:17 ` Suresh Siddha
2008-07-22 20:20 ` [PATCH] x86: move declaring x2apic_extra_bits Yinghai Lu
2008-07-24 11:00 ` Ingo Molnar
2008-07-26 2:39 ` [PATCH] x86: add apic probe for genapic 64bit - fix Yinghai Lu
2008-07-26 14:32 ` Ingo Molnar
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=86802c440807221140o20dcc31fjc10f86a22a1125bb@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®