From: Peter Zijlstra <peterz@infradead.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Qais Yousef <qais.yousef@arm.com>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
hsinyi@chromium.org, Joel Fernandes <joelaf@google.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Quentin Perret <qperret@google.com>,
ctheegal@codeaurora.org, Guenter Roeck <groeck@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cros_ec_spi: Even though we're RT priority, don't bump cpu freq
Date: Wed, 24 Jun 2020 17:56:32 +0200 [thread overview]
Message-ID: <20200624155632.GJ4781@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAD=FV=WuYZRO=sv4ODr0SFk0gTtvCW0dNQXbFGrBDqRgjYv-jA@mail.gmail.com>
On Thu, Jun 18, 2020 at 02:18:23PM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Jun 12, 2020 at 5:52 AM Qais Yousef <qais.yousef@arm.com> wrote:
> >
> > On 06/10/20 15:18, Douglas Anderson wrote:
> > > + struct sched_attr sched_attr = {
> > > + .sched_policy = SCHED_FIFO,
> > > + .sched_priority = MAX_RT_PRIO / 2,
> > > + .sched_flags = SCHED_FLAG_UTIL_CLAMP_MIN,
> > > + .sched_util_min = 0,
> >
> > Hmm I thought Peter already removed all users that change RT priority directly.
> >
> > https://lore.kernel.org/lkml/20200422112719.826676174@infradead.org/
>
> Yeah, I mentioned that patch series "after the cut" in my patch and
> also made sure to CC Peter on my patch. I'm not sure what happened to
> that series since I don't see it in linuxnext...
Right, I got busy with other stuff and it languished a bit.
I tried to merge it recently (it's actually in tip/sched/fifo atm), but
then 0day robot found a problem with it and I've not yet had the time to
deal with that.
Specifically these patches unEXPORT the schet_setscheduler() family, but
kernel/trace/ring_buffer_benchmark.c can still be a module :-(
prev parent reply other threads:[~2020-06-24 15:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 22:18 Douglas Anderson
2020-06-11 11:03 ` Quentin Perret
2020-06-11 17:48 ` Doug Anderson
2020-06-12 9:24 ` Quentin Perret
2020-06-12 12:34 ` Qais Yousef
2020-06-12 13:47 ` Quentin Perret
2020-06-12 14:00 ` Qais Yousef
2020-06-18 21:31 ` Doug Anderson
2020-06-19 15:31 ` Qais Yousef
2020-06-22 18:19 ` Doug Anderson
2020-06-23 15:56 ` Qais Yousef
2020-06-12 12:52 ` Qais Yousef
2020-06-18 21:18 ` Doug Anderson
2020-06-19 15:38 ` Qais Yousef
2020-06-22 18:21 ` Doug Anderson
2020-06-23 16:40 ` Qais Yousef
2020-06-24 15:49 ` Joel Fernandes
2020-06-24 16:55 ` Qais Yousef
2020-06-24 17:35 ` Joel Fernandes
2020-06-24 17:52 ` Qais Yousef
2020-06-24 17:55 ` Joel Fernandes
2020-06-24 18:29 ` Doug Anderson
2020-06-25 14:20 ` Qais Yousef
2020-06-24 16:01 ` Peter Zijlstra
2020-06-24 17:14 ` Qais Yousef
2020-06-24 15:56 ` 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=20200624155632.GJ4781@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bleung@chromium.org \
--cc=ctheegal@codeaurora.org \
--cc=dianders@chromium.org \
--cc=drinkcat@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=hsinyi@chromium.org \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qais.yousef@arm.com \
--cc=qperret@google.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
all inboxes | Powered by JetHome®