[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87frd4zgku.ffs@tglx>
Date: Tue, 02 Sep 2025 23:32:01 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Kaiwan N Billimoria <kaiwan.billimoria@...il.com>
Cc: Llillian@...r-ark.net, agordeev@...ux.ibm.com,
akpm@...ux-foundation.org, alexander.shishkin@...ux.intel.com,
anna-maria@...utronix.de, bigeasy@...utronix.de, catalin.marinas@....com,
chenhuacai@...nel.org, francesco@...la.it, frederic@...nel.org,
guoweikang.kernel@...il.com, jstultz@...gle.com, kpsingh@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
mark.rutland@....com, maz@...nel.org, mingo@...nel.org, pmladek@...e.com,
rrangel@...omium.org, sboyd@...nel.org, urezki@...il.com, v-singh1@...com,
will@...nel.org, peterz@...radead.org, elver@...gle.com,
namcao@...utronix.de
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot
timestamp
On Tue, Sep 02 2025 at 19:09, Kaiwan N. Billimoria wrote:
> Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
>> Under the assumption that nothing on the way resets the counter.
> Ah. Is there any known component - within ROM/BL stages/kernel code - that does
> this?
How should I know? I'm not playing with this boot timing muck and yes,
some hardware counters can be reset by software...
> Forgive my asking, but if fine, will this (above-mentioned) patch be taken? So,
> knowing that, we can proceed forward..
Just send a patch with a proper justification and we take from there.
Thanks,
tglx
Powered by blists - more mailing lists