From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
linux-rt-users@vger.kernel.org, mingo@elte.hu, ego@in.ibm.com,
dipankar@in.ibm.com, tytso@us.ibm.com, dvhltc@us.ibm.com,
akpm@linux-foundation.org, josh@freedesktop.org,
tglx@linutronix.de, niv@us.ibm.com,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] fix misplaced mb() in rcu_enter/exit_nohz()
Date: Tue, 18 Mar 2008 07:10:40 -0700 [thread overview]
Message-ID: <20080318141040.GB8222@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080318124248.GB8669@osiris.boeblingen.de.ibm.com>
On Tue, Mar 18, 2008 at 01:42:48PM +0100, Heiko Carstens wrote:
> On Mon, Mar 17, 2008 at 01:43:57PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 17, 2008 at 11:17:41PM +0300, Oleg Nesterov wrote:
> > > (to clarify: my question is completely offtopic to this patch)
> > > On 03/17, Paul E. McKenney wrote:
> > > > On Mon, Mar 17, 2008 at 09:30:47PM +0300, Oleg Nesterov wrote:
> > > > > I'm not sure the code below is up to date, but what I have in
> > > > > arch/s390/kernel/time.c is:
> > > > >
> > > > > stop_hz_timer:
> > > > >
> > > > > cpu_set(cpu, nohz_cpu_mask);
> > > > >
> > > > > if (rcu_needs_cpu(cpu) || local_softirq_pending()) {
> > > > > cpu_clear(cpu, nohz_cpu_mask);
> > > > > return;
> > > > > }
> > > > >
> > > > > Don't we need smp_mb() after cpu_set() ?
> > > >
> > > > S390's memory model is quite strong, so it might not be needed.
> > >
> > > OK, in that case we shouldn't worry.
> >
> > I don't know if I would go -that- far. ;-)
>
> Not sure if I can follow you here, but for the smp case cpu_set() is
> nothing but a set_bit() which implies both: a memory barrier and a compiler
> barrier on s390. The compare and swap instruction used here ensures that
> all previous memory accesses will be seen by other cpus.
That should make this work as far as I can see!
Thanx, Paul
> Btw. the code sequence above will go away soon anyway, since I'm converting
> our code to the generic NO_HZ infrastructure.
>
> > > > In any
> > > > case, if needed, it goes -before- the cpu_set(), because the problems
> > > > would arise if prior RCU read-side critical sections were to be reordered
> > > > to follow this cpu_set(), right?
> > >
> > > No, but it is very possible I missed something.
> > >
> > > What if rcu_needs_cpu(cpu) is executed before cpu_set(cpu, nohz_cpu_mask)?
> > > It can miss rcu_start_batch() -> rcp->cur++ and return false, but at the
> > > same time rcu_start_batch() may see nohz_cpu_mask without this CPU.
> >
> > If you mean that the rcu_needs_cpu() executes before the cpu_set() in
> > the code fragment above, while the rcu_start_batch() executes on some
> > other CPU?
>
> That should never happen because of the compiler and memory barrier semantics
> of cpu_set(). Or... I'm completely misunderstanding you, which wouldn't me
> surprise me too much :)
prev parent reply other threads:[~2008-03-19 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 1:08 [PATCH] fix misplaced mb() in rcu_enter/exit_nohz() Paul E. McKenney
2008-03-17 3:09 ` Nick Piggin
2008-03-17 5:54 ` Paul E. McKenney
2008-03-17 15:43 ` Steven Rostedt
2008-03-17 18:30 ` Oleg Nesterov
2008-03-17 19:06 ` Paul E. McKenney
2008-03-17 20:17 ` Oleg Nesterov
2008-03-17 20:43 ` Paul E. McKenney
2008-03-17 21:23 ` Oleg Nesterov
2008-03-18 12:42 ` Heiko Carstens
2008-03-18 14:10 ` Paul E. McKenney [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=20080318141040.GB8222@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=oleg@tv-sign.ru \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tytso@us.ibm.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