From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] nohz: Remove tick_nohz_idle_enter_norcu() / tick_nohz_idle_exit_norcu()
Date: Mon, 21 Nov 2011 08:37:45 -0800 [thread overview]
Message-ID: <20111121163745.GA2323@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111121152345.GA25088@somewhere.redhat.com>
On Mon, Nov 21, 2011 at 04:23:51PM +0100, Frederic Weisbecker wrote:
> On Sun, Nov 20, 2011 at 09:28:19PM -0800, Paul E. McKenney wrote:
> > On Mon, Nov 21, 2011 at 02:46:58AM +0100, Frederic Weisbecker wrote:
> > > 2011/11/19 Paul E. McKenney <paulmck@linux.vnet.ibm.com>:
> > > > On Thu, Nov 17, 2011 at 05:03:44PM -0800, Paul E. McKenney wrote:
> > > >> On Thu, Nov 17, 2011 at 12:11:34PM -0800, Josh Triplett wrote:
[ . . . ]
> > 4. Task A invokes a system call. If the system-call entry
> > code were to again invoke rcu_idle_enter(), then my patch
> > is required. If you check and avoid invoking rcu_idle_enter()
> > in this case, then my patch is not required.
>
> You mean rcu_idle_exit()? So yeah, since we have the tick running
> and thus RCU not in extended QS, we won't call rcu_idle_exit() on syscall
> entry.
OK, then I will drop my patch. ;-)
Thanx, Paul
prev parent reply other threads:[~2011-11-21 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 17:48 [PATCH] nohz: Remove tick_nohz_idle_enter_norcu() / tick_nohz_idle_exit_norcu() Frederic Weisbecker
2011-11-17 20:11 ` Josh Triplett
2011-11-18 1:03 ` Paul E. McKenney
2011-11-19 0:50 ` Paul E. McKenney
2011-11-21 1:46 ` Frederic Weisbecker
2011-11-21 5:28 ` Paul E. McKenney
2011-11-21 15:23 ` Frederic Weisbecker
2011-11-21 16:37 ` 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=20111121163745.GA2323@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).