From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Cochran <richardcochran@gmail.com>,
John Stultz <jstultz@google.com>
Cc: "Mahesh Bandewar (महेश बंडेवा" <maheshb@google.com>,
Netdev <netdev@vger.kernel.org>,
Linux <linux-kernel@vger.kernel.org>,
"David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Don Hatchett" <hatch@google.com>,
"Yuliang Li" <yuliangli@google.com>,
"Mahesh Bandewar" <mahesh@bandewar.net>,
"Stephen Boyd" <sboyd@kernel.org>
Subject: Re: [PATCH 1/4] time: add ktime_get_cycles64() api
Date: Mon, 09 Oct 2023 16:48:56 +0200 [thread overview]
Message-ID: <87o7h7q2av.ffs@tglx> (raw)
In-Reply-To: <ZRiP9mgFjLpKHj8N@hoboy.vegasvil.org>
On Sat, Sep 30 2023 at 14:15, Richard Cochran wrote:
> 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.
Correct. Exposing the raw counter value is broken if the counter wraps
around on a regular base.
Thanks,
tglx
next prev parent reply other threads:[~2023-10-09 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 2:37 [PATCH 1/4] time: add ktime_get_cycles64() api Mahesh Bandewar
2023-09-29 5:15 ` John Stultz
2023-09-29 6:34 ` Mahesh Bandewar (महेश बंडेवार)
2023-09-29 6:56 ` John Stultz
2023-09-29 7:06 ` John Stultz
2023-09-30 21:15 ` Richard Cochran
2023-10-09 14:48 ` Thomas Gleixner [this message]
2023-10-03 0:12 ` Mahesh Bandewar (महेश बंडेवार)
2023-10-03 2:32 ` John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7h7q2av.ffs@tglx \
--to=tglx@linutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hatch@google.com \
--cc=jstultz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=yuliangli@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.