linux-kernel - Re: [PATCH] cros_ec_spi: Even though we're RT priority, don't bump cpu freq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 24 Jun 2020 17:56:32 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Doug Anderson <dianders@...omium.org>
Cc:     Qais Yousef <qais.yousef@....com>,
        Benson Leung <bleung@...omium.org>,
        Enric Balletbo i Serra <enric.balletbo@...labora.com>,
        hsinyi@...omium.org, Joel Fernandes <joelaf@...gle.com>,
        Nicolas Boichat <drinkcat@...omium.org>,
        Gwendal Grignou <gwendal@...omium.org>,
        Quentin Perret <qperret@...gle.com>, ctheegal@...eaurora.org,
        Guenter Roeck <groeck@...omium.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cros_ec_spi: Even though we're RT priority, don't bump
 cpu freq

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@....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 :-(