Re: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot
"Roberto A. Foglietta" <[email protected]> Thu, 16 Apr 2026 00:24:59 +0200
| Newsgroups | org.kernel.vger.linux-embedded,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAJGKYO4PatnJLPVuwp730hEEqsMCEAravO-cS6xyenMNJEsXtQ@mail.gmail.com> |
On Wed, 15 Apr 2026 at 23:57, Roberto A. Foglietta <[email protected]> wrote: > [...] > V5 > > A single file with the essential for hacking the early boot, early_times.h -- it means before every feature offered by the kernel is available or 100% trustable, thus ASM because it is also supposed to fix what is broken in the kernel thus using the kernel macros isn't the correct way to do so. Early times means before the kernel, thus also out-of-it-three or feature support. Them asm (isb) sounds too drastic or not enough for "exhotic" arm arch? It is a template to start with, not a working part of the kernel. When the kernel works, !0 == true is true. The concept remains the same: a register counter read protected by fencing. Not more, not less than the essential. And a bucket out-of-the-three as a starting point **before** the kernel is ready or fixed. Written in this way, does it sound more reasonable? Best regards, R-