From: Tejun Heo <tj@kernel.org>
To: paulmck@linux.vnet.ibm.com
Cc: mingo@elte.hu, peterz@infradead.org,
linux-kernel@vger.kernel.org,
Dipankar Sarma <dipankar@in.ibm.com>,
Josh Triplett <josh@freedesktop.org>,
Oleg Nesterov <oleg@redhat.com>,
Dimitri Sivanich <sivanich@sgi.com>
Subject: Re: [PATCH 3/4 UPDATED] scheduler: replace migration_thread with cpu_stop
Date: Fri, 07 May 2010 07:24:00 +0200 [thread overview]
Message-ID: <4BE3A3F0.3000906@kernel.org> (raw)
In-Reply-To: <20100506184252.GC2325@linux.vnet.ibm.com>
> And of course, I overdid it in my patch when I removed smp_mb() from
> the !SMP version of synchronize_sched_expedited(). :-/
>
> If synchronize_sched_expedited() is ever to be invoked from within
> kernel/sched.c in a UP kernel, there needs to be a "barrier()" in the
> !SMP version. So please see the following patch.
Thanks. Pushed.
--
tejun
next prev parent reply other threads:[~2010-05-07 5:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 13:47 [PATCHSET sched/core] cpu_stop: implement and use cpu_stop, take#2 Tejun Heo
2010-05-04 13:47 ` [PATCH 1/4] cpu_stop: implement stop_cpu[s]() Tejun Heo
2010-05-04 13:47 ` [PATCH 2/4] stop_machine: reimplement using cpu_stop Tejun Heo
2010-05-04 13:47 ` [PATCH 3/4] scheduler: replace migration_thread with cpu_stop Tejun Heo
2010-05-05 1:33 ` Paul E. McKenney
2010-05-05 7:28 ` Tejun Heo
2010-05-05 17:47 ` Paul E. McKenney
2010-05-05 18:10 ` [PATCH 3/4 UPDATED] " Tejun Heo
2010-05-05 20:31 ` Paul E. McKenney
2010-05-06 16:30 ` Tejun Heo
2010-05-06 18:42 ` Paul E. McKenney
2010-05-07 5:24 ` Tejun Heo [this message]
2010-05-04 13:47 ` [PATCH 4/4] scheduler: kill paranoia check in synchronize_sched_expedited() Tejun Heo
2010-05-04 18:52 ` [PATCHSET sched/core] cpu_stop: implement and use cpu_stop, take#2 Peter Zijlstra
2010-05-05 7:30 ` Tejun Heo
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=4BE3A3F0.3000906@kernel.org \
--to=tj@kernel.org \
--cc=dipankar@in.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sivanich@sgi.com \
/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).