From: Tim Chen <tim.c.chen@linux.intel.com>
To: Ramses <ramses@well-founded.dev>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Power Management <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Yu Chen <yu.c.chen@intel.com>,
srinivas.pandruvada@linux.intel.com
Subject: Re: Fwd: Intel hybrid CPU scheduler always prefers E cores
Date: Tue, 28 Nov 2023 15:10:48 -0800 [thread overview]
Message-ID: <c2a9ceb3d7b1f384ad94d10b7058bb1cebea3d07.camel@linux.intel.com> (raw)
In-Reply-To: <NkN3JYx--3-9@well-founded.dev>
On Tue, 2023-11-28 at 23:33 +0100, Ramses wrote:
> I applied the patch on top of 6.6.2, but unfortunately I see more or less the same behaviour as before, with single-threaded CPU-bound tasks running almost exclusively on E cores.
>
> Ramses
I suspect that you may have other issues. I wonder if CPU priorities are getting
assigned properly on your system.
Saw in the original bugzilla
https://bugzilla.kernel.org/show_bug.cgi?id=218195
that you don't see /proc/sys/kernel/sched_itmt_enabled which
may be a symptom of such a problem.
+Srinivas, is there something Ramses can do to help
find out if there are issues with cppc?
Tim
next prev parent reply other threads:[~2023-11-28 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:22 Fwd: Intel hybrid CPU scheduler always prefers E cores Bagas Sanjaya
2023-11-28 14:02 ` Peter Zijlstra
2023-11-28 14:19 ` Bagas Sanjaya
2023-12-18 16:11 ` Ricardo Neri
2023-11-28 17:33 ` Tim Chen
2023-11-28 22:37 ` Ramses
[not found] ` <NkN3JYx--3-9@well-founded.dev>
2023-11-28 23:10 ` Tim Chen [this message]
2023-11-28 23:17 ` Ramses
2023-11-29 15:05 ` srinivas pandruvada
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=c2a9ceb3d7b1f384ad94d10b7058bb1cebea3d07.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bagasdotme@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=ramses@well-founded.dev \
--cc=regressions@lists.linux.dev \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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