[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXyOsFomVyQNlMof@gmail.com>
Date: Fri, 30 Jan 2026 03:07:52 -0800
From: Breno Leitao <leitao@...ian.org>
To: Baoquan He <bhe@...hat.com>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
kernel-team@...a.com, kexec@...ts.infradead.org, dyoung@...hat.com,
tony.luck@...el.com, xueshuai@...ux.alibaba.com, vgoyal@...hat.com,
zhiquan1.li@...el.com, olja@...a.com
Subject: Re: [PATCH] vmcore_info: expose hardware error recovery statistics
via sysfs
On Fri, Jan 30, 2026 at 09:59:58AM +0800, Baoquan He wrote:
> On 01/29/26 at 05:34am, Breno Leitao wrote:
> > Add a sysfs file at /sys/kernel/vmcore_stats and expose hardware error
> > recovery statistics that are already tracked by the kernel. This allows
> > userspace monitoring tools to track recovered hardware errors without
> > requiring kernel crashes.
>
> I don't understand. If w/o requring kernel crashes, why do you call it
> vmcore_stats? It's a normal showing of hardware error recovery
> statistics tracked by kernel, can we name it /sys/kernel/hwerr_stats?
Agreed, /sys/kernel/hwerr_stats is a much better name. Thank you for the
suggestion!
> It's obviously having nothiing to do with vmcore, isn't it?
You're correct. The only connection is that this functionality currently
resides in kernel/vmcore_info.c. I initially thought it would make sense
to create a generic sysfs entry for vmcore, but I can see now that this
caused more confusion than clarification.
I'll update the patch accordingly.
Thanks,
--breno
Powered by blists - more mailing lists