[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250902133920.973210-1-kaiwan.billimoria@gmail.com>
Date: Tue, 2 Sep 2025 19:09:08 +0530
From: Kaiwan N Billimoria <kaiwan.billimoria@...il.com>
To: tglx@...utronix.de
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
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?
Forgive my asking, but if fine, will this (above-mentioned) patch be taken? So,
knowing that, we can proceed forward..
Thanks,
Kaiwan.
Powered by blists - more mailing lists