From: Matt Turner <mattst88@gmail.com>
To: Magnus Lindholm <linmag7@gmail.com>
Cc: richard.henderson@linaro.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Re: [PATCH v7 5/5] alpha: decode Clipper environmental events and retain console logs
Date: Tue, 13 Oct 2026 22:10:20 -0400 [thread overview]
Message-ID: <20261014021020.3842132-3-mattst88@gmail.com> (raw)
In-Reply-To: <20261013211551.991723-6-linmag7@gmail.com>
On Tue, Oct 13, 2026 at 23:15 +0200, Magnus Lindholm wrote:
> Remove the redundant silent first pass now that every valid environmental
> notification is reported.
The silent pass only existed in v6, so this is a change between
versions. It belongs below the --- line.
> +# define EL_TYPE__REGATTA__TSUNAMI_PCHIP0_EXTENDED (6)
> +# define EL_TYPE__REGATTA__TSUNAMI_PCHIP1_EXTENDED (7)
Where are these two types and their register layout described? I could
not find them in the 21272 HRM or the ES40 Service Guide.
> +static int
> +clipper_process_environment(struct el_common *header, int print)
With the silent pass gone, the only caller passes print = 1 and ignores
the return value. Both can go.
> + if (packet->class != EL_CLASS__HEADER || packet->revision != 1)
> + return false;
el_process_header_subpacket() prints the frame name and, for event and
halt frames, the timestamp. This scanner prints nothing for the
wrapper, so a decoded log no longer says when the error happened, and
the halt code is dropped too. Please print them here as well.
> + default:
> + return false;
Your changelog says the ES40 record is class 5, type 4, which lands
here. So on the one machine this ran on, the log is never decoded or
cleared, and each boot dumps up to 1 KiB of hex per CPU. Please split
the scanner into its own patch so the environmental decode does not
wait on it.
> + for (i = 0; i < dump; i++) {
> + if (!(i & 15))
> + printk("%s %04zx:", err_print_prefix, i);
> + printk(KERN_CONT " %02x", data[i]);
> + if ((i & 15) == 15 || i + 1 == dump)
> + printk(KERN_CONT "\n");
> + }
print_hex_dump() does this:
print_hex_dump(err_print_prefix, " ", DUMP_PREFIX_OFFSET, 16, 1,
data, dump, false);
> +static struct el_subpacket_handler tsunami_subpacket_handler =
> + SUBPACKET_HANDLER_INIT(EL_CLASS__REGATTA_FAMILY, tsunami_process_subpacket);
Nothing reaches this. tsunami_console_log() calls the function
directly, and the handler list is only walked from
cdl_check_console_data_log(), err_ev7.c and err_marvel.c. Drop the
registration and the three functions can be __init.
next prev parent reply other threads:[~2026-10-14 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 21:15 [PATCH v7 0/5] alpha: improve Tsunami machine check reporting Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 1/5] alpha: move Tsunami machine check handling to err_tsunami.c Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 2/5] alpha: describe the Tsunami system machine check frame Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 3/5] alpha: bound EV6 logout decoding by the processor area Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 4/5] alpha: decode and acknowledge Tsunami system machine checks Magnus Lindholm
2026-10-14 2:10 ` Matt Turner
2026-10-13 21:15 ` [PATCH v7 5/5] alpha: decode Clipper environmental events and retain console logs Magnus Lindholm
2026-10-14 2:10 ` Matt Turner [this message]
2026-10-14 2:10 ` [PATCH v7 0/5] alpha: improve Tsunami machine check reporting Matt Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261014021020.3842132-3-mattst88@gmail.com \
--to=mattst88@gmail.com \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®