Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 12 Jun 2020 15:00:31 +0100
From:   Qais Yousef <qais.yousef@arm.com>
To:     Quentin Perret <qperret@google.com>
Cc:     Doug Anderson <dianders@chromium.org>,
        Benson Leung <bleung@chromium.org>,
        Enric Balletbo i Serra <enric.balletbo@collabora.com>,
        hsinyi@chromium.org, Joel Fernandes <joelaf@google.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Nicolas Boichat <drinkcat@chromium.org>,
        Gwendal Grignou <gwendal@chromium.org>,
        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
Message-ID: <20200612140031.4rrnbmdcb3hv755h@e107158-lin.cambridge.arm.com>
References: <20200610151818.1.I666ecd9c6f3c6405bd75831a21001b8109b6438c@changeid>
 <20200611110301.GA132747@google.com>
 <CAD=FV=V2FvFcYrghxUSdHNxmcS3DKpnBbk2oL64w7hh=tV-DfQ@mail.gmail.com>
 <20200612092454.GA94228@google.com>
 <20200612123448.fcmzv3rdtsbawmpd@e107158-lin.cambridge.arm.com>
 <20200612134721.GA142550@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200612134721.GA142550@google.com>
User-Agent: NeoMutt/20171215
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 06/12/20 14:47, Quentin Perret wrote:

[...]

> > > > somehow measure whether or not the task is making its deadlines and
> > > > boost the CPU frequency up if deadlines are not being met.  I'm sure
> > > > there are fancier ways.
> > 
> > You need to use SCHED_DEADLINE then :)
> 
> Well, not quite :-)
> 
> The frequency selection for DL is purely based on the userspace-provided
> parameters, from which we derive the bandwidth request. But we don't do
> things like 'raise the frequency if the actual runtime gets close to the
> WCET', or anything of the sort. All of that would have to be implemented
> in userspace ATM.

Hmm okay. I am not a deadline expert so sorry if I was misleading. But it's the
only scheduling class that has the concept of deadline.

Cheers

--
Qais Yousef