[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANDhNCroULekKiCyUYMPuUe+=XVJriiJvJmC3wrhkC10Bxtt3Q@mail.gmail.com>
Date: Wed, 3 May 2023 19:59:44 -0700
From: John Stultz <jstultz@...gle.com>
To: "liujian (CE)" <liujian56@...wei.com>
Cc: Frank Woo <frankwoo@...gle.com>, Rhine Wu <Rhinewuwu@...gle.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"sboyd@...nel.org" <sboyd@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [Question] softlockup in run_timer_softirq
On Wed, May 3, 2023 at 6:50 PM liujian (CE) <liujian56@...wei.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?
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
Powered by blists - more mailing lists