From: Peter Zijlstra <peterz@infradead.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"bsegall@google.com" <bsegall@google.com>,
"bristot@redhat.com" <bristot@redhat.com>,
"chris.hyser@oracle.com" <chris.hyser@oracle.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"efault@gmx.de" <efault@gmx.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"joel@joelfernandes.org" <joel@joelfernandes.org>,
"joshdon@google.com" <joshdon@google.com>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"kprateek.nayak@amd.com" <kprateek.nayak@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"patrick.bellasi@matbug.net" <patrick.bellasi@matbug.net>,
Pavel Machek <pavel@ucw.cz>, "pjt@google.com" <pjt@google.com>,
"qperret@google.com" <qperret@google.com>,
"qyousef@layalina.io" <qyousef@layalina.io>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"timj@gnu.org" <timj@gnu.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"youssefesmat@chromium.org" <youssefesmat@chromium.org>,
"yu.c.chen@intel.com" <yu.c.chen@intel.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] sched/fair: fix pick_eevdf to always find the correct se
Date: Thu, 5 Oct 2023 17:11:23 +0200 [thread overview]
Message-ID: <20231005151123.GD743@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20231005150258.GA36277@noisy.programming.kicks-ass.net>
On Thu, Oct 05, 2023 at 05:02:58PM +0200, Peter Zijlstra wrote:
> 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've killed the patch for now, will try again once we figure out what
goes side-ways.
Thanks!
prev parent reply other threads:[~2023-10-05 15:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 7:31 [PATCH] sched/fair: fix pick_eevdf to always find the correct se Biju Das
2023-10-05 7:58 ` Biju Das
[not found] ` <ZR6A/lsQMP+ymD1f@chenyu5-mobl2.ccr.corp.intel.com>
2023-10-05 9:31 ` Biju Das
2023-10-05 15:02 ` Peter Zijlstra
2023-10-05 15:08 ` Biju Das
2023-10-06 8:36 ` Marek Szyprowski
2023-10-06 9:38 ` Biju Das
[not found] ` <553e2ee4-ab3a-4635-a74f-0ba4cc03f3f9@samsung.com>
2023-10-06 10:31 ` Mike Galbraith
2023-10-06 14:00 ` Peter Zijlstra
2023-10-06 14:39 ` Mike Galbraith
2023-10-06 15:55 ` Peter Zijlstra
2023-10-06 16:54 ` Mike Galbraith
2023-10-06 19:24 ` Peter Zijlstra
2023-10-06 20:15 ` Marek Szyprowski
2023-10-06 23:27 ` Mike Galbraith
2023-10-07 0:37 ` Chen Yu
2023-10-07 6:26 ` Biju Das
2023-10-07 6:42 ` Chen Yu
2023-10-09 14:27 ` Phil Auld
2023-10-10 2:08 ` Chen Yu
2023-10-07 6:24 ` Biju Das
2023-10-05 15:11 ` Peter Zijlstra [this message]
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=20231005151123.GD743@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=patrick.bellasi@matbug.net \
--cc=pavel@ucw.cz \
--cc=pjt@google.com \
--cc=qperret@google.com \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=timj@gnu.org \
--cc=vincent.guittot@linaro.org \
--cc=youssefesmat@chromium.org \
--cc=yu.c.chen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox