[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221107115848.GA4588@lothringen>
Date: Mon, 7 Nov 2022 12:58:48 +0100
From: Frederic Weisbecker <frederic@...nel.org>
To: Anna-Maria Behnsen <anna-maria@...utronix.de>
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
John Stultz <jstultz@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Eric Dumazet <edumazet@...gle.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Arjan van de Ven <arjan@...radead.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Rik van Riel <riel@...riel.com>,
Richard Cochran <richardcochran@...il.com>
Subject: Re: [PATCH v4 07/16] timer: Retrieve next expiry of
pinned/non-pinned timers seperately
On Fri, Nov 04, 2022 at 03:57:28PM +0100, Anna-Maria Behnsen wrote:
> For the conversion of the NOHZ timer placement to a pull at expiry time
> model it's required to have seperate expiry times for the pinned and the
> non-pinned (movable) timers. Therefore struct timer_events is introduced.
>
> No functional change
>
> Originally-by: Richard Cochran (linutronix GmbH) <richardcochran@...il.com>
> Signed-off-by: Anna-Maria Behnsen <anna-maria@...utronix.de>
Reviewed-by: Frederic Weisbecker <frederic@...nel.org>
Powered by blists - more mailing lists