From: Thomas Gleixner <tglx@linutronix.de>
To: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
Cc: Llillian@star-ark.net, agordeev@linux.ibm.com,
akpm@linux-foundation.org, alexander.shishkin@linux.intel.com,
anna-maria@linutronix.de, bigeasy@linutronix.de,
catalin.marinas@arm.com, chenhuacai@kernel.org,
francesco@valla.it, frederic@kernel.org,
guoweikang.kernel@gmail.com, jstultz@google.com,
kpsingh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
maz@kernel.org, mingo@kernel.org, pmladek@suse.com,
rrangel@chromium.org, sboyd@kernel.org, urezki@gmail.com,
v-singh1@ti.com, will@kernel.org,
Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
Date: Tue, 02 Sep 2025 12:52:37 +0200 [thread overview]
Message-ID: <87a53d2kju.ffs@tglx> (raw)
In-Reply-To: <20250902070253.936687-1-kaiwan.billimoria@gmail.com>
On Tue, Sep 02 2025 at 12:32, Kaiwan N. Billimoria wrote:
> So, just confirming: here 1409443611 divided by 200 MHz gives us 7.047218055s
> since boot, and thus the actual timestamp here is that plus 0.000001s yes?
> (Over 7s here? yes, it's just that I haven't yet setup U-Boot properly for uSD
> card boot, thus am manually loading commands in U-Boot to boot up, that's all).
Looks about right.
> A question (perhaps very stupid): will the hwcnt - the output of the read() -
> be guaranteed to be (close to) the number of increments since processor
> power-up (or reset)? Meaning, it's simply a hardware feature and agnostic to
> what code the core was executing (ROM/BL/kernel), yes?
Under the assumption that nothing on the way resets the counter.
Thanks
tglx
next prev parent reply other threads:[~2025-09-02 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 4:40 [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp vishnu singh
2025-08-23 22:53 ` Thomas Gleixner
2025-08-23 23:12 ` Thomas Gleixner
2025-09-01 4:05 ` Kaiwan N Billimoria
2025-09-01 5:57 ` Kaiwan N Billimoria
2025-09-02 7:02 ` [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp Kaiwan N Billimoria
2025-09-02 10:52 ` Thomas Gleixner [this message]
2025-09-02 13:39 ` Kaiwan N Billimoria
2025-09-02 21:32 ` Thomas Gleixner
2025-08-24 4:35 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2025-08-23 4:19 vishnu singh
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=87a53d2kju.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Llillian@star-ark.net \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=francesco@valla.it \
--cc=frederic@kernel.org \
--cc=guoweikang.kernel@gmail.com \
--cc=jstultz@google.com \
--cc=kaiwan.billimoria@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=pmladek@suse.com \
--cc=rrangel@chromium.org \
--cc=sboyd@kernel.org \
--cc=urezki@gmail.com \
--cc=v-singh1@ti.com \
--cc=will@kernel.org \
/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.