From: Frederic Weisbecker <frederic@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH 4/8] rcu/nocb: Trigger self-IPI on late deferred wake up before user resume
Date: Mon, 11 Jan 2021 13:35:10 +0100 [thread overview]
Message-ID: <20210111123510.GD242508@lothringen> (raw)
In-Reply-To: <X/w+yJmCBnDWxtoE@hirez.programming.kicks-ass.net>
On Mon, Jan 11, 2021 at 01:04:24PM +0100, Peter Zijlstra wrote:
> > +static DEFINE_PER_CPU(struct irq_work, late_wakeup_work) =
> > + IRQ_WORK_INIT(late_wakeup_func);
> > +
> > /**
> > * rcu_user_enter - inform RCU that we are resuming userspace.
> > *
> > @@ -692,9 +704,17 @@ noinstr void rcu_user_enter(void)
> > struct rcu_data *rdp = this_cpu_ptr(&rcu_data);
> >
> > lockdep_assert_irqs_disabled();
> > - do_nocb_deferred_wakeup(rdp);
> > + /*
> > + * We may be past the last rescheduling opportunity in the entry code.
> > + * Trigger a self IPI that will fire and reschedule once we resume to
> > + * user/guest mode.
> > + */
> > + if (do_nocb_deferred_wakeup(rdp) && need_resched())
> > + irq_work_queue(this_cpu_ptr(&late_wakeup_work));
> > +
> > rcu_eqs_enter(true);
> > }
>
> Do we have the guarantee that every architecture that supports NOHZ_FULL
> has arch_irq_work_raise() on?
Yes it's a requirement for NOHZ_FULL to work. But you make me realize this
is tacit and isn't constrained anywhere in the code. I'm going to add
HAVE_IRQ_WORK_RAISE and replace the weak definition with a config
based.
>
> Also, can't you do the same thing you did earlier and do that wakeup
> thing before we complete exit_to_user_mode_prepare() ?
I do it for CONFIG_GENERIC_ENTRY but the other architectures have their own
exit to user loop that I would need to audit and make sure that interrupts aren't
ever re-enabled before resuming to user and there is no possible rescheduling
point. I could manage to handle arm and arm64 but the others scare me:
$ git grep HAVE_CONTEXT_TRACKING
arch/csky/Kconfig: select HAVE_CONTEXT_TRACKING
arch/mips/Kconfig: select HAVE_CONTEXT_TRACKING
arch/powerpc/Kconfig: select HAVE_CONTEXT_TRACKING if PPC64
arch/riscv/Kconfig: select HAVE_CONTEXT_TRACKING
arch/sparc/Kconfig: select HAVE_CONTEXT_TRACKING
:-s
next prev parent reply other threads:[~2021-01-11 12:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 2:05 [RFC PATCH 0/8] rcu/sched: Fix ignored rescheduling after rcu_eqs_enter() v3 Frederic Weisbecker
2021-01-09 2:05 ` [RFC PATCH 1/8] rcu: Remove superfluous rdp fetch Frederic Weisbecker
2021-01-09 9:03 ` Greg KH
2021-01-10 10:59 ` Frederic Weisbecker
2021-01-09 2:05 ` [RFC PATCH 2/8] rcu: Pull deferred rcuog wake up to rcu_eqs_enter() callers Frederic Weisbecker
2021-01-09 2:05 ` [RFC PATCH 3/8] rcu/nocb: Perform deferred wake up before last idle's need_resched() check Frederic Weisbecker
2021-01-09 2:05 ` [RFC PATCH 4/8] rcu/nocb: Trigger self-IPI on late deferred wake up before user resume Frederic Weisbecker
2021-01-11 12:04 ` Peter Zijlstra
2021-01-11 12:35 ` Frederic Weisbecker [this message]
2021-01-09 2:05 ` [RFC PATCH 5/8] entry: Explicitly flush pending rcuog wakeup before last rescheduling points Frederic Weisbecker
2021-01-11 0:40 ` Frederic Weisbecker
2021-01-11 5:13 ` Paul E. McKenney
2021-01-11 11:50 ` Frederic Weisbecker
2021-01-11 12:08 ` Peter Zijlstra
2021-01-11 12:54 ` Frederic Weisbecker
2021-01-09 2:05 ` [RFC PATCH 6/8] sched: Report local wake up on resched blind zone within idle loop Frederic Weisbecker
2021-01-11 12:25 ` Peter Zijlstra
2021-01-11 12:56 ` Frederic Weisbecker
2021-01-12 8:24 ` [sched] 9720a64438: WARNING:at_kernel/sched/core.c:#sched_resched_local_assert_allowed kernel test robot
2021-01-12 8:24 ` kernel test robot
[not found] ` <161062476680.19482.8402362019173198799@build.alporthouse.com>
2021-01-14 15:19 ` [RFC PATCH 6/8] sched: Report local wake up on resched blind zone within idle loop Paul E. McKenney
2021-01-09 2:05 ` [RFC PATCH 7/8] entry: Report local wake up on resched blind zone while resuming to user Frederic Weisbecker
2021-01-13 2:46 ` [entry] 8e01c5f104: unixbench.score -2.2% regression kernel test robot
2021-01-13 2:46 ` kernel test robot
2021-01-09 2:05 ` [RFC PATCH 8/8] timer: Report ignored local enqueue in nohz mode Frederic Weisbecker
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=20210111123510.GD242508@lothringen \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.