From: Andi Kleen <ak@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
manpreet@fabric7.com,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
discuss@x86-64.org
Subject: Re: [PATCH] i386/x86-64: Fix timer SMP bootup race
Date: Sun, 16 Jan 2005 06:34:24 +0100 [thread overview]
Message-ID: <20050116053424.GB2489@wotan.suse.de> (raw)
In-Reply-To: <1105849247.5711.4.camel@localhost.localdomain>
On Sun, Jan 16, 2005 at 03:20:47PM +1100, Rusty Russell wrote:
> On Sat, 2005-01-15 at 08:59 +0100, Andi Kleen wrote:
> > I think my patch is better. It at least keeps all the
> > baggage out of the normal run paths. Doing this check at each timer interrupt
> > doesn't make much sense.
>
> It doesn't penalize the architectures which do the right thing already.
> If this weren't i386 we were talking about...
>
> But adding a bizarro "pre-prepare" notifier verged on nonsensical 8(. I
I don't see the big issue. Preparse is just not as early as you thought.
> prefer an explicit "init_timers_early()" call as a workaround; I'll code
> that up and test tomorrow, when I'm back in the office with an SMP box
> to test.
>
> I'm also not clear on why we need to enable interrupts around
> calibrate_delay() on secondary processors, but I'll try that too and
> find out 8)
Because you cannot calibrate the timer without a timer tick.
Even if you changed that it wouldn't help because the race can
as well happen in the idle loop on the secondaries.
-Andi
next prev parent reply other threads:[~2005-01-16 5:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 4:09 Andi Kleen
2005-01-15 5:09 ` Rusty Russell
2005-01-15 5:23 ` Andi Kleen
2005-01-15 7:34 ` Rusty Russell
2005-01-15 7:40 ` Andrew Morton
2005-01-15 7:59 ` Andi Kleen
2005-01-16 4:20 ` Rusty Russell
2005-01-16 5:34 ` Andi Kleen [this message]
2005-01-16 6:42 ` Rusty Russell
2005-01-15 6:28 ` Andrew Morton
2005-01-15 6:43 ` Andi Kleen
2005-01-15 6:54 ` Andrew Morton
2005-01-15 7:18 ` Andi Kleen
2005-01-17 2:34 ` Rusty Russell
2005-01-17 5:43 ` Andi Kleen
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=20050116053424.GB2489@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manpreet@fabric7.com \
--cc=rusty@rustcorp.com.au \
/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®