From: Andi Kleen <ak@muc.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Per-cpu patches on top of PDA stuff...
Date: 20 Sep 2006 18:09:05 +0200
Date: Wed, 20 Sep 2006 18:09:05 +0200 [thread overview]
Message-ID: <20060920160905.GA47657@muc.de> (raw)
In-Reply-To: <1158756868.9633.0.camel@mulgrave.il.steeleye.com>
On Wed, Sep 20, 2006 at 08:54:28AM -0400, James Bottomley wrote:
> On Wed, 2006-09-20 at 09:00 +0200, Andi Kleen wrote:
> > boot CPU == 0 should be true. You just can't assume anything about its
> > APIC ID, but we decouple APIC ID and logical processor id anyways.
>
> No, it is not. Voyager has fixed and immutable CPU IDs dependent on CPU
> position in the system. If CPU 0 is missing or logically deconfigured,
> the boot CPU is definitely non zero.
As APIC ID (hard_smp_processor_id()) possible, but surely not as linux logical
processor id (smp_processor_id()). That always starts with 0 and goes up.
-Andi
next prev parent reply other threads:[~2006-09-20 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 3:13 Per-cpu patches on top of PDA stuff Rusty Russell
2006-09-19 8:03 ` Rusty Russell
2006-09-19 8:26 ` Andi Kleen
2006-09-19 20:39 ` Jeremy Fitzhardinge
2006-09-19 8:14 ` Jeremy Fitzhardinge
2006-09-19 21:03 ` Chris Wright
2006-09-19 22:36 ` Jeremy Fitzhardinge
2006-09-20 0:07 ` Rusty Russell
2006-09-20 7:00 ` Andi Kleen
2006-09-20 12:54 ` James Bottomley
2006-09-20 16:09 ` Andi Kleen [this message]
2006-09-20 16:15 ` James Bottomley
2006-09-20 16:22 ` Andi Kleen
2006-09-20 16:42 ` James Bottomley
2006-09-20 17:49 ` Andi Kleen
2006-09-20 18:10 ` James Bottomley
2006-09-20 18:42 ` Andi Kleen
2006-09-21 8:54 ` Rusty Russell
2006-09-19 20:37 ` Chris Wright
2006-09-19 20:40 ` Jeremy Fitzhardinge
2006-09-19 21:08 ` Chris Wright
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=20060920160905.GA47657@muc.de \
--to=ak@muc.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.