From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH 0/3] tick: Fix softirq related warnings
Date: Tue, 8 Feb 2022 16:52:31 -0800 [thread overview]
Message-ID: <20220209005231.GW4285@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220208161635.544701-1-frederic@kernel.org>
On Tue, Feb 08, 2022 at 05:16:32PM +0100, Frederic Weisbecker wrote:
> Some cleanups and debug rework.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/core
>
> HEAD: 18b00369d58da4c73946d5f8ebed8e8c7ade89e2
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (3):
> tick/rcu: Remove obsolete rcu_needs_cpu() parameters
> tick/rcu: Stop allowing RCU_SOFTIRQ in idle
> lib/irq_poll: Declare IRQ_POLL softirq vector as ksoftirqd-parking safe
I have queued these for local testing, but I am guessing that you would
like them to go up some other path.
Thanx, Paul
> include/linux/interrupt.h | 11 ++++++++-
> include/linux/rcutiny.h | 3 +--
> include/linux/rcutree.h | 2 +-
> kernel/rcu/tree.c | 3 +--
> kernel/time/tick-sched.c | 60 ++++++++++++++++++++++++++++++++++-------------
> 5 files changed, 57 insertions(+), 22 deletions(-)
next prev parent reply other threads:[~2022-02-09 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:16 Frederic Weisbecker
2022-02-08 16:16 ` [PATCH 1/3] tick/rcu: Remove obsolete rcu_needs_cpu() parameters Frederic Weisbecker
2022-02-08 16:16 ` [PATCH 2/3] tick/rcu: Stop allowing RCU_SOFTIRQ in idle Frederic Weisbecker
2022-02-08 16:16 ` [PATCH 3/3] lib/irq_poll: Declare IRQ_POLL softirq vector as ksoftirqd-parking safe Frederic Weisbecker
2022-02-09 0:52 ` Paul E. McKenney [this message]
2022-02-14 5:46 ` [PATCH 0/3] tick: Fix softirq related warnings Paul Menzel
2022-02-14 16:29 ` Paul E. McKenney
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=20220209005231.GW4285@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmenzel@molgen.mpg.de \
--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
all inboxes | Powered by JetHome®