On Tue, 26 Mar 2019 at 11:36, Rafael J. Wysocki wrote:
>
> On Mon, Mar 25, 2019 at 3:24 PM Ulf Hansson wrote:
> >
> > On Mon, 25 Mar 2019 at 13:21, Rafael J. Wysocki wrote:
> > >
> > > On Wednesday, February 27, 2019 8:58:35 PM CET Ulf Hansson wrote:
> > > > To be able to predict the sleep
On Mon, Mar 25, 2019 at 3:24 PM Ulf Hansson wrote:
>
> On Mon, 25 Mar 2019 at 13:21, Rafael J. Wysocki wrote:
> >
> > On Wednesday, February 27, 2019 8:58:35 PM CET Ulf Hansson wrote:
> > > To be able to predict the sleep duration for a CPU that is entering idle,
> > > knowing when the next
On Mon, 25 Mar 2019 at 13:21, Rafael J. Wysocki wrote:
>
> On Wednesday, February 27, 2019 8:58:35 PM CET Ulf Hansson wrote:
> > To be able to predict the sleep duration for a CPU that is entering idle,
> > knowing when the next timer/tick is going to expire, is extremely useful.
> > Both the teo
On Wednesday, February 27, 2019 8:58:35 PM CET Ulf Hansson wrote:
> To be able to predict the sleep duration for a CPU that is entering idle,
> knowing when the next timer/tick is going to expire, is extremely useful.
> Both the teo and the menu cpuidle governors already makes use of this
>
On 27/02/2019 20:58, Ulf Hansson wrote:
> To be able to predict the sleep duration for a CPU that is entering idle,
> knowing when the next timer/tick is going to expire, is extremely useful.
> Both the teo and the menu cpuidle governors already makes use of this
> information, while selecting an
To be able to predict the sleep duration for a CPU that is entering idle,
knowing when the next timer/tick is going to expire, is extremely useful.
Both the teo and the menu cpuidle governors already makes use of this
information, while selecting an idle state.
Moving forward, the similar
6 matches
Mail list logo
