On Fri, Jan 25, 2019 at 11:04 AM Ulf Hansson wrote:
>
> [...]
>
> > > > > > +/**
> > > > > > + * tick_nohz_get_next_wakeup - return the next wake up of the CPU
> > > > > > + * @cpu: the particular CPU to get next wake up for
> > > > > > + *
> > > > > > + * Called for idle CPUs only.
> > > > > > +
[...]
> > > > > +/**
> > > > > + * tick_nohz_get_next_wakeup - return the next wake up of the CPU
> > > > > + * @cpu: the particular CPU to get next wake up for
> > > > > + *
> > > > > + * Called for idle CPUs only.
> > > > > + */
> > > > > +ktime_t tick_nohz_get_next_wakeup(int cpu)
> > > > > +{
On Wed, 16 Jan 2019 at 11:59, Rafael J. Wysocki wrote:
>
> On Wed, Jan 16, 2019 at 8:58 AM Ulf Hansson wrote:
> >
> > On Fri, 11 Jan 2019 at 12:07, Rafael J. Wysocki wrote:
> > >
> > > On Thursday, November 29, 2018 6:46:36 PM CET Ulf Hansson wrote:
> > > > From: Lina Iyer
> > > >
> > > >
On Wed, Jan 16, 2019 at 8:58 AM Ulf Hansson wrote:
>
> On Fri, 11 Jan 2019 at 12:07, Rafael J. Wysocki wrote:
> >
> > On Thursday, November 29, 2018 6:46:36 PM CET Ulf Hansson wrote:
> > > From: Lina Iyer
> > >
> > > Knowing the sleep duration of CPUs, is known to be needed while selecting
> >
On Fri, 11 Jan 2019 at 12:07, Rafael J. Wysocki wrote:
>
> On Thursday, November 29, 2018 6:46:36 PM CET Ulf Hansson wrote:
> > From: Lina Iyer
> >
> > Knowing the sleep duration of CPUs, is known to be needed while selecting
> > the most energy efficient idle state for a CPU or a group of CPUs.
On Thursday, November 29, 2018 6:46:36 PM CET Ulf Hansson wrote:
> From: Lina Iyer
>
> Knowing the sleep duration of CPUs, is known to be needed while selecting
> the most energy efficient idle state for a CPU or a group of CPUs.
>
> However, to be able to compute the sleep duration, we need to
6 matches
Mail list logo