[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180314171950.yn5spehwzuc5nttu@lakrids.cambridge.arm.com>
Date: Wed, 14 Mar 2018 17:19:51 +0000
From: Mark Rutland <mark.rutland@....com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Sudeep Holla <sudeep.holla@....com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
linux-pm@...r.kernel.org, Kevin Hilman <khilman@...nel.org>,
Lina Iyer <ilina@...eaurora.org>,
Lina Iyer <lina.iyer@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...nel.org>,
Juri Lelli <juri.lelli@....com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 06/25] timer: Export next wakeup time of a CPU
On Wed, Mar 14, 2018 at 05:58:16PM +0100, Ulf Hansson wrote:
> @@ -132,6 +133,15 @@ static inline ktime_t tick_nohz_get_sleep_length(void)
> {
> return NSEC_PER_SEC / HZ;
> }
> +
> +static inline ktime_t tick_nohz_get_next_wakeup(int cpu)
> +{
> + ktime_t len = NSEC_PER_SEC/HZ;
> +
> + /* Next wake up is the tick period, assume it starts now */
> + return ktime_add(len, ktime_get());
> +}
Thsi could be marginally simpler as:
static inline ktime_t tick_nohz_get_next_wakeup(int cpu)
{
/* Next wake up is the tick period, assume it starts now */
return ktime_add(tick_nohz_get_sleep_length(), ktime_get());
}
Thanks,
Mark.
Powered by blists - more mailing lists