From: Alison Chaiken <achaiken@aurora.tech>
To: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
Cc: "Chang, Junxiao" <junxiao.chang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"Peh, Hock Zhang" <hock.zhang.peh@intel.com>,
Glenn Elliott <glenn@aurora.tech>
Subject: Re: [PATCH] softirq: wake up ktimer thread in softirq context
Date: Mon, 23 Jan 2023 10:04:20 -0800 [thread overview]
Message-ID: <CAFzL-7upCjPPyB-9tHf4E4=M+GFot2fnH9t7M5x9cKikUMxB+w@mail.gmail.com> (raw)
In-Reply-To: <Y6H4zqr8bObRFE1g@linutronix.de>
On Tue, Dec 20, 2022 at 10:03 AM bigeasy@linutronix.de
<bigeasy@linutronix.de> wrote:
>
> On 2022-12-20 10:44:07 [+0000], Chang, Junxiao wrote:
> > Any comment? This patch is for 6.1-rt, issue could be reproduced with 5.19-rt kernel as well.
>
> Thanks for the ping. I did see the initial email and I didn't get to it
> yet. I need to re-test, confirm and then apply.
> The ktimer patch is not in v5.15 and this is currently the latest one
> maintained by the stable team. I don't know which one will be the
> following LTS kernel but this one needs to have this addressed. The
> v5.19 is not receiving any updates.
> Given the current timing, I will look into this in January.
>
> > Regards,
> > Junxiao
>
> Sebastian
Any further thoughts about Junxiao Chang's patch? We backported
ktimer patches from Sebastian and Frederic to 5.15 and would like this
fix it is sensible.
Thanks,
Alison Chaiken
Aurora Innovation
next prev parent reply other threads:[~2023-01-23 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:56 [PATCH] softirq: wake up ktimer thread in softirq context Junxiao Chang
2022-12-20 10:44 ` Chang, Junxiao
2022-12-20 17:10 ` Alison Chaiken
2022-12-20 18:02 ` bigeasy
2022-12-20 19:28 ` Alison Chaiken
2023-01-23 18:04 ` Alison Chaiken [this message]
2023-02-10 15:32 ` Alison Chaiken
2023-02-10 16:33 ` bigeasy
2023-02-17 17:30 ` Sebastian Andrzej Siewior
2023-02-20 8:55 ` Chang, Junxiao
2023-02-20 10:53 ` Sebastian Andrzej Siewior
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='CAFzL-7upCjPPyB-9tHf4E4=M+GFot2fnH9t7M5x9cKikUMxB+w@mail.gmail.com' \
--to=achaiken@aurora.tech \
--cc=bigeasy@linutronix.de \
--cc=glenn@aurora.tech \
--cc=hock.zhang.peh@intel.com \
--cc=junxiao.chang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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).