Re: [PATCH v3] printk: fix zero-valued printk timestamps in early boot

On Wed, Apr 01 2026 at 11:12, Steven Rostedt wrote:
> On Wed, 01 Apr 2026 10:33:26 +0200
> Thomas Gleixner <[email protected]> wrote:
>> As I've demonstrated the time until the first time stamp is available
>> has nothing to do with the number of CPUs and is more or less constant:
>
> So my question is, if something changes in this time frame, where it goes
> from 30ms to 300ms, how would we find out?
>
> Again, for Chromebooks, we get these timestamps from the firmware and it's
> very useful.

I understand all of that and I'm not opposed to make that happen if it's
integrated properly into sched clock as I demonstrated with the PoC
hack.

Thanks,

        tglx