From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Matt Mackall <mpm@selenic.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.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 17:26:07 -0700 [thread overview]
Message-ID: <4637DA9F.3030503@goop.org> (raw)
In-Reply-To: <20070501222432.GP11166@waste.org>
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?
>
My understanding is that the boot CPU is random depending on who wins
the "I get to boot" bunfight.
J
next prev parent reply other threads:[~2007-05-02 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 16:38 [PATCH] fix dynticks for voyager James Bottomley
2007-04-30 22:13 ` Thomas Gleixner
2007-05-01 22:24 ` Matt Mackall
2007-05-02 0:26 ` Jeremy Fitzhardinge [this message]
2007-05-02 0:47 ` James Bottomley
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=4637DA9F.3030503@goop.org \
--to=jeremy@goop.org \
--cc=James.Bottomley@HansenPartnership.com \
--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