From: Steven Rostedt <rostedt@goodmis.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jason Baron <jbaron@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
mingo@elte.hu
Subject: Re: [PATCH] jump_label_inc may return before the code is patched
Date: Wed, 02 Nov 2011 11:42:22 -0400 [thread overview]
Message-ID: <1320248542.4793.34.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111102152123.GF14726@redhat.com>
On Wed, 2011-11-02 at 17:21 +0200, Gleb Natapov wrote:
> On Tue, Oct 18, 2011 at 05:06:25PM -0400, Steven Rostedt wrote:
> > On Tue, 2011-10-18 at 19:55 +0200, Gleb Natapov wrote:
> > > If cpu A calls jump_label_inc() just after atomic_add_return() is
> > > called by cpu B, atomic_inc_not_zero() will return value greater then
> > > zero and jump_label_inc() will return to a caller before jump_label_update()
> > > finishes its job on cpu B.
> >
> > OK, I see what you are saying. There's a race here that jump_label_inc
> > may return before jump labels are actually activated. I have no issue
> > with this change. This guarantees that jump labels will be active on
> > return of jump_label_inc().
> >
> > I'm assuming that jump_label_update() does memory barries, as it does
> > modify code, and would be itself a synchronization point.
> >
> > Acked-by: Steven Rostedt <rostedt@goodmis.org>
> >
> So through what tree this should go to Linus' git?
I'll pull it in. I'm currently scrambling around getting back up to
speed after a 11 day conference spree.
-- Steve
next prev parent reply other threads:[~2011-11-02 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 17:55 Gleb Natapov
2011-10-18 20:54 ` Jason Baron
2011-10-19 7:03 ` Gleb Natapov
2011-10-18 21:06 ` Steven Rostedt
2011-11-02 15:21 ` Gleb Natapov
2011-11-02 15:42 ` Steven Rostedt [this message]
2011-11-18 23:12 ` [tip:perf/core] jump_label: " tip-bot for Gleb Natapov
2011-12-06 6:27 ` tip-bot for Gleb Natapov
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=1320248542.4793.34.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=gleb@redhat.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®