From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sofirq: make rcu_irq_enter()/rcu_irq_exit() called in pairs
Date: Tue, 27 Oct 2009 07:30:43 -0700 [thread overview]
Message-ID: <20091027143043.GI6645@linux.vnet.ibm.com> (raw)
In-Reply-To: <4AE6A88B.8000004@cn.fujitsu.com>
On Tue, Oct 27, 2009 at 04:00:11PM +0800, Lai Jiangshan wrote:
>
> irq_enter() calls rcu_irq_enter() unconditionally,
> the same as irq_exit() calls rcu_irq_exit().
>
> It does not change the binary because rcu_irq_enter()
> is dummy when !CONFIG_NO_HZ.
>
> It's just a cleanup.
This does look like a nice cleanup! I will pull it in and test it.
Yes, it should be provably the same, but RCU has taught me to be quite
paranoid. ;-)
Thanx, Paul
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index f8749e5..21939d9 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -302,9 +302,9 @@ void irq_exit(void)
> if (!in_interrupt() && local_softirq_pending())
> invoke_softirq();
>
> + rcu_irq_exit();
> #ifdef CONFIG_NO_HZ
> /* Make sure that timer wheel updates are propagated */
> - rcu_irq_exit();
> if (idle_cpu(smp_processor_id()) && !in_interrupt() && !need_resched())
> tick_nohz_stop_sched_tick(0);
> #endif
>
prev parent reply other threads:[~2009-10-27 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 8:00 [PATCH] sofirq: make rcu_irq_enter()/rcu_irq_exit() called in pairs Lai Jiangshan
2009-10-27 14:30 ` 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=20091027143043.GI6645@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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