Re: [PATCH v8 6/6] alpha: add bounded Clipper console-log scanning

[Matt Turner]

On Thu, Oct 15, 2026 at 6:24 AM Magnus Lindholm <linmag7@xxxxxxxxx> wrote:
>
> Clipper console logs have an HWRPB byte count. Bound wrapper and child
> traversal by that count before decoding embedded processor and system
> logout frames. Print the wrapper name and event/halt timestamp, halt
> code, and recorded CPU ID for processor packets.
>
> Acknowledge the log only after a complete termination packet. Retain the
> firmware pointer on unknown or incomplete wrappers and print at most
> 1 KiB of raw bytes using print_hex_dump(). This avoids the generic
> scanner's unconditional acknowledgment after a parsing failure.
>
> The ES40 record observed during testing is class 5, type 4. Its wrapper
> layout is unknown and remains raw and unacknowledged; it may therefore
> be printed again at each boot. Successful decoding of a nonempty hardware
> log remains unverified. Keep console scanning independent of the live
> machine-check and environmental handlers and restrict it to Clipper.
>
> Console environmental payloads also remain raw: ES40 Service Guide
> Table D-18's sys_offset conflicts with its field offsets. No register
> layout is assumed for unverified extended subpacket types 6 and 7.
>
> The scanner invokes the payload decoder directly during PCI init; no
> generic subpacket-handler registration is needed. Mark its helpers
> __init and retain the PCI init hook in sys_dp264.c.
>
> Signed-off-by: Magnus Lindholm <linmag7@xxxxxxxxx>

Reviewed-by: Matt Turner <mattst88@xxxxxxxxx>