[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <OS0PR01MB5922C4CF327492EE2A0B2BA586C9A@OS0PR01MB5922.jpnprd01.prod.outlook.com>
Date: Fri, 6 Oct 2023 09:38:03 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: Marek Szyprowski <m.szyprowski@...sung.com>,
Peter Zijlstra <peterz@...radead.org>
CC: "bsegall@...gle.com" <bsegall@...gle.com>,
"bristot@...hat.com" <bristot@...hat.com>,
"chris.hyser@...cle.com" <chris.hyser@...cle.com>,
"corbet@....net" <corbet@....net>,
"dietmar.eggemann@....com" <dietmar.eggemann@....com>,
"efault@....de" <efault@....de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"joel@...lfernandes.org" <joel@...lfernandes.org>,
"joshdon@...gle.com" <joshdon@...gle.com>,
"juri.lelli@...hat.com" <juri.lelli@...hat.com>,
"kprateek.nayak@....com" <kprateek.nayak@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"patrick.bellasi@...bug.net" <patrick.bellasi@...bug.net>,
Pavel Machek <pavel@....cz>, "pjt@...gle.com" <pjt@...gle.com>,
"qperret@...gle.com" <qperret@...gle.com>,
"qyousef@...alina.io" <qyousef@...alina.io>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"tim.c.chen@...ux.intel.com" <tim.c.chen@...ux.intel.com>,
"timj@....org" <timj@....org>,
"vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
"youssefesmat@...omium.org" <youssefesmat@...omium.org>,
"yu.c.chen@...el.com" <yu.c.chen@...el.com>,
"mgorman@...e.de" <mgorman@...e.de>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>
Subject: RE: [PATCH] sched/fair: fix pick_eevdf to always find the correct se
> Subject: Re: [PATCH] sched/fair: fix pick_eevdf to always find the correct
> se
>
> On 05.10.2023 17:08, Biju Das wrote:
> > Hi Peter Zijlstra,
> >
> >> Subject: Re: [PATCH] sched/fair: fix pick_eevdf to always find the
> >> correct se
> >>
> >> On Thu, Oct 05, 2023 at 07:31:34AM +0000, Biju Das wrote:
> >>
> >>> [ 26.099203] EEVDF scheduling fail, picking leftmost
> >> This, that the problem.. the rest is just noise because printk stinks.
> >>
> >> Weirdly have not seen that trigger, and I've been running with this
> >> patch on for a few days now :/
> > I agree Original issue is "EEVDF scheduling fail, picking leftmost"
> > Which is triggering noisy lock warning messages during boot.
> >
> > 2 platforms are affected both ARM platforms(Renesas and Samsung) Maybe
> > other platforms affected too.
>
>
> Just to note, I've run into this issue on the QEmu's 'arm64/virt'
> platform, not on the Samsung specific hardware.
OK, if needed I am happy to test on the real hardware, if a fix found for this issue. It is 100% reproducible Renesas RZ/g2L SMARC EVK platform.
Cheers,
Biju
Powered by blists - more mailing lists