From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Breno Leitao <leitao@debian.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
"Moore, Robert" <robert.moore@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"acpica-devel@lists.linux.dev" <acpica-devel@lists.linux.dev>,
"kernel-team@meta.com" <kernel-team@meta.com>
Subject: Re: [PATCH] ghes: Track number of recovered hardware errors
Date: Mon, 14 Jul 2025 19:35:56 +0200 [thread overview]
Message-ID: <20250714173556.GQaHU__LL6IUIPCDIW@fat_crate.local> (raw)
In-Reply-To: <SJ1PR11MB6083C38E6DA922E05E1748D6FC54A@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Mon, Jul 14, 2025 at 05:33:45PM +0000, Luck, Tony wrote:
> > If you're going to do this, then you can perhaps make this variable always
> > present so that you don't need an export and call it "hardware_errors_count"
> > or so and all machinery which deals with RAS - GHES, MCE, AER, bla, can
> > increment it...
>
> Not sure I'd want to see all the different classes of errors bundled together
> in a single count. I think MCE recovery is quite robust and rarely leads to
> subsequent kernel problems.
That's what I said. And a RAS tool can give that info already.
But for some reason Breno still wants that info somewhere else.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-07-14 17:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 16:57 Breno Leitao
2025-07-14 17:10 ` Luck, Tony
2025-07-14 17:10 ` Borislav Petkov
2025-07-14 17:33 ` Luck, Tony
2025-07-14 17:35 ` Borislav Petkov [this message]
2025-07-14 22:21 ` Luck, Tony
2025-07-15 8:29 ` Borislav Petkov
2025-07-15 10:20 ` Breno Leitao
2025-07-15 10:31 ` Borislav Petkov
2025-07-15 12:02 ` Breno Leitao
2025-07-15 12:53 ` Borislav Petkov
2025-07-15 13:46 ` Shuai Xue
2025-07-15 15:09 ` Borislav Petkov
2025-07-16 2:05 ` Shuai Xue
2025-07-16 6:30 ` Mauro Carvalho Chehab
2025-07-15 17:25 ` Breno Leitao
2025-07-16 3:04 ` Shuai Xue
2025-07-16 12:42 ` Breno Leitao
2025-07-17 3:03 ` Shuai Xue
2025-07-17 12:06 ` Breno Leitao
2025-07-17 17:19 ` Luck, Tony
2025-07-17 17:39 ` Breno Leitao
2025-07-17 17:54 ` Luck, Tony
2025-07-15 10:07 ` Breno Leitao
2025-07-15 10:18 ` Borislav Petkov
2025-07-17 16:06 ` Breno Leitao
2025-07-17 17:29 ` Luck, Tony
2025-07-18 16:11 ` Breno Leitao
2025-07-18 17:36 ` Luck, Tony
2025-07-21 8:56 ` Breno Leitao
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=20250714173556.GQaHU__LL6IUIPCDIW@fat_crate.local \
--to=bp@alien8.de \
--cc=acpica-devel@lists.linux.dev \
--cc=james.morse@arm.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=tony.luck@intel.com \
/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®