From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Wen Yang <wenyang.linux@foxmail.com>,
paul.gortmaker@windriver.com, LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] tick/rcu: fix false positive "softirq work is pending" messages on RT
Date: Fri, 01 Sep 2023 11:56:39 +0200 [thread overview]
Message-ID: <87il8u43oo.ffs@tglx> (raw)
In-Reply-To: <20230831133214.XF2yjiEb@linutronix.de>
On Thu, Aug 31 2023 at 15:32, Sebastian Andrzej Siewior wrote:
> On 2023-08-28 17:03:39 [+0200], Frederic Weisbecker wrote:
>> > Frederic would normally take this, but he appears to be out. So I am
>> > (probably only temporarily) queueing this in -rcu for more testing
>> > coverage.
>>
>> I'm back, I should relay this to Thomas to avoid conflicts with
>> timers changes.
>
> I somehow missed this thread and I do see this if I enable NO_HZ. I lost
> it…
> Anyway, I'm going to pick it up for RT and ping the timer department
> after the merge window.
It's queued in timers/urgent and will hit Linus tree before rc1
next prev parent reply other threads:[~2023-09-01 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 20:07 [PATCH] tick/rcu: fix false positive "softirq work is pending" messages on RT paul.gortmaker
2023-08-20 17:23 ` Wen Yang
2023-08-21 22:03 ` Paul E. McKenney
2023-08-28 15:03 ` Frederic Weisbecker
2023-08-31 13:32 ` Sebastian Andrzej Siewior
2023-09-01 9:56 ` Thomas Gleixner [this message]
2023-08-24 16:00 ` Ahmad Fatoum
2023-08-30 10:30 ` [tip: timers/urgent] tick/rcu: Fix false positive "softirq work is pending" messages tip-bot2 for Paul Gortmaker
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=87il8u43oo.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=wenyang.linux@foxmail.com \
/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.