From: "liujian (CE)" <liujian56@huawei.com>
To: John Stultz <jstultz@google.com>
Cc: Frank Woo <frankwoo@google.com>, Rhine Wu <Rhinewuwu@google.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [Question] softlockup in run_timer_softirq
Date: Fri, 5 May 2023 19:37:41 +0800 [thread overview]
Message-ID: <29864a44-c548-3de9-7053-25915e7e0702@huawei.com> (raw)
In-Reply-To: <CANDhNCroULekKiCyUYMPuUe+=XVJriiJvJmC3wrhkC10Bxtt3Q@mail.gmail.com>
On 2023/5/4 10:59, John Stultz wrote:
> On Wed, May 3, 2023 at 6:50 PM liujian (CE) <liujian56@huawei.com> wrote:
>> On 2023/5/2 11:06, John Stultz wrote:
>>> So I wanted to revive this old thread, as Frank Woo mentioned his team
>>> has seen a similar issue as well.
>>>
>>> Liujian: I'm curious if you've made any further progress with your
>>> adapted patch ontop of PeterZ's softirq_needs_break patch series?
>>>
>> Hi John,
>> Only the commit ("softirq, timer: Use softirq_needs_break()") is
>> added to the patchset of Peter, and no other modification is made.
>>> Might it be worth re-submitting the whole series for consideration upstream?
>>>
>> I agree very much and expect, because we often encounter similar
>> problems when doing fuzzy tests (especially when the test machine is poor).
>
> Ok. Will you submit the series + your patch to the list for review and
> consideration then?
>
The patch[1] has been sent out. Please help review it. Thank you very much.
[1]
https://lore.kernel.org/lkml/20230505113315.3307723-1-liujian56@huawei.com/
> Please include Frank and Rhine on CC so they can validate and provide
> Tested-by: tags if it works for them as well.
>
> thanks
> -john
next prev parent reply other threads:[~2023-05-05 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:50 liujian (CE)
2023-02-13 20:00 ` John Stultz
2023-02-15 8:34 ` liujian (CE)
2023-05-02 3:06 ` John Stultz
2023-05-04 1:49 ` liujian (CE)
2023-05-04 2:59 ` John Stultz
2023-05-05 11:37 ` liujian (CE) [this message]
2023-03-03 10:55 ` liujian (CE)
2023-03-09 7:04 ` John Stultz
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=29864a44-c548-3de9-7053-25915e7e0702@huawei.com \
--to=liujian56@huawei.com \
--cc=Rhinewuwu@google.com \
--cc=frankwoo@google.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sboyd@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 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®