From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
arjanvandeven@gmail.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86: clean up smpboot.c's use of udelay+schedule
Date: Tue, 31 Jan 2012 14:01:56 +0100 [thread overview]
Message-ID: <1328014916.2446.217.camel@twins> (raw)
In-Reply-To: <20120131125331.GE4408@elte.hu>
On Tue, 2012-01-31 at 13:53 +0100, Ingo Molnar wrote:
> Wanna give a short TODO list to anyone wanting to work on that?
I paged out most details again, but it goes something like:
- read and understand the current generic code
- and all architecture code, at which point you'll probably boggle
at all the similarities that are all subtly different (there's
about 3 actually different ways in the arch code).
- pick one, preferably one that keeps additional state and doesn't
fully rely on the online bits and pull it into generic code and
provide a small vector of arch specific functions.
- convert all archs over.
Also related:
- figure out why cpu_down needs kstopmachine, I'm not sure it does..
we should be able to tear down a cpu using synchronize_sched() and a
single stop_one_cpu(). (someday when there's time I might actually
try to implement this).
next prev parent reply other threads:[~2012-01-31 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 4:53 x86: clean up smpboot.c's use of udelay+schedule Arjan van de Ven
2012-01-31 12:43 ` Ingo Molnar
2012-01-31 12:47 ` Peter Zijlstra
2012-01-31 12:53 ` Ingo Molnar
2012-01-31 13:01 ` Peter Zijlstra [this message]
2012-02-02 0:33 ` Paul E. McKenney
2012-02-02 8:03 ` Srivatsa S. Bhat
2012-02-02 15:23 ` Paul E. McKenney
2012-02-03 17:32 ` Paul E. McKenney
2012-01-31 13:43 ` Arjan van de Ven
2012-01-31 13:32 ` Arjan van de Ven
2012-01-31 14:30 ` 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=1328014916.2446.217.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=arjanvandeven@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).