From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: 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>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ramses VdP <ramses@well-founded.dev>,
ricardo.neri-calderon@linux.intel.com
Subject: Re: Fwd: Intel hybrid CPU scheduler always prefers E cores
Date: Tue, 28 Nov 2023 21:19:18 +0700 [thread overview]
Message-ID: <9b424bac-b15c-476d-893e-9e6b54de70c3@gmail.com> (raw)
In-Reply-To: <20231128140225.GS8262@noisy.programming.kicks-ass.net>
On 11/28/23 21:02, Peter Zijlstra wrote:
> On Tue, Nov 28, 2023 at 08:22:27PM +0700, Bagas Sanjaya wrote:
>> Hi,
>>
>> I come across an interesting bug report on Bugzilla [1]. The reporter
>> wrote:
>
> Thanks for forwarding, what happend in bugzilla staysi in bugzilla etc..
>
> Did you perchance Cc the reporter?
>
Yes, I CC'ed him.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-11-28 14:19 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 [this message]
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
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=9b424bac-b15c-476d-893e-9e6b54de70c3@gmail.com \
--to=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=ricardo.neri-calderon@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/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