[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZRiP9mgFjLpKHj8N@hoboy.vegasvil.org>
Date: Sat, 30 Sep 2023 14:15:34 -0700
From: Richard Cochran <richardcochran@...il.com>
To: John Stultz <jstultz@...gle.com>
Cc: Mahesh Bandewar
(महेश बंडेवार) <maheshb@...gle.com>,
Netdev <netdev@...r.kernel.org>,
Linux <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Jonathan Corbet <corbet@....net>,
Don Hatchett <hatch@...gle.com>,
Yuliang Li <yuliangli@...gle.com>,
Mahesh Bandewar <mahesh@...dewar.net>,
Thomas Gleixner <tglx@...utronix.de>,
Stephen Boyd <sboyd@...nel.org>
Subject: Re: [PATCH 1/4] time: add ktime_get_cycles64() api
On Fri, Sep 29, 2023 at 12:06:46AM -0700, John Stultz wrote:
> But I still think we should avoid exporting the raw cycle values
> unless there is some extremely strong argument for it
Looks like the argument was based on a misunderstanding of what
CLOCK_MONOTONIC_RAW actually is. So, please, let's not expose the raw
cycle counter value.
Thanks,
Richard
Powered by blists - more mailing lists