From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Matt Mackall <mpm@selenic.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix dynticks for voyager
Date: Tue, 01 May 2007 19:47:39 -0500 [thread overview]
Message-ID: <1178066859.4320.90.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <4637DA9F.3030503@goop.org>
On Tue, 2007-05-01 at 17:26 -0700, Jeremy Fitzhardinge wrote:
> Matt Mackall wrote:
> > On Mon, Apr 30, 2007 at 11:38:51AM -0500, James Bottomley wrote:
> >
> >> As usual voyager tripped over an explicit boot CPU is zero assumption in
> >> the dynticks code. This is the fix I have queued in the voyager tree.
> >>
> >
> > Can we flush out all these assumptions by adding a constant offset
> > somewhere? Or reversing the ordering?
It might be useful to voyager, but unless the offset were random, people
would simply hardwire it.
> My understanding is that the boot CPU is random depending on who wins
> the "I get to boot" bunfight.
Not quite. On apic systems, the boot CPU can be an arbitrary physical
id but is conventionally logical id 0. On voyager, the CPU id actually
maps to a fixed location, so there's no sense in having a logical id.
The booting CPU on voyager is simply the lowest numbered CPU that comes
up through the SUS boot.
James
prev parent reply other threads:[~2007-05-02 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 16:38 James Bottomley
2007-04-30 22:13 ` Thomas Gleixner
2007-05-01 22:24 ` Matt Mackall
2007-05-02 0:26 ` Jeremy Fitzhardinge
2007-05-02 0:47 ` James Bottomley [this message]
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=1178066859.4320.90.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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®