[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANDhNCoqYhFNfuyArrt0Sj7sWoLNsVJUn7YCUuxEL8nFrZPHog@mail.gmail.com>
Date: Thu, 12 Jun 2025 17:03:30 -0700
From: John Stultz <jstultz@...gle.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
Richard Cochran <richardcochran@...il.com>, Christopher Hall <christopher.s.hall@...el.com>,
Frederic Weisbecker <frederic@...nel.org>, Anna-Maria Behnsen <anna-maria@...utronix.de>,
Miroslav Lichvar <mlichvar@...hat.com>, Werner Abt <werner.abt@...nberg-usa.com>,
David Woodhouse <dwmw2@...radead.org>, Stephen Boyd <sboyd@...nel.org>,
Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
Kurt Kanzenbach <kurt@...utronix.de>, Nam Cao <namcao@...utronix.de>,
Antoine Tenart <atenart@...nel.org>
Subject: Re: [patch V2 04/26] timekeeping: Introduce timekeeper ID
On Mon, May 19, 2025 at 1:33 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> From: Anna-Maria Behnsen <anna-maria@...utronix.de>
>
> As long as there is only a single timekeeper, there is no need to clarify
> which timekeeper is used. But with the upcoming reusage of the timekeeper
> infrastructure for auxiliary clock timekeepers, an ID is required to
> differentiate.
>
> Introduce an enum for timekeeper IDs, introduce a field in struct tk_data
> to store this timekeeper id and add also initialization. The id struct
> field is added at the end of the second cachline, as there is a 4 byte hole
> anyway.
>
> Signed-off-by: Anna-Maria Behnsen <anna-maria@...utronix.de>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
>
Acked-by: John Stultz <jstultz@...gle.com>
thanks
-john
Powered by blists - more mailing lists