Linux EDAC development
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Christopher BeSerra <beserra@amazon.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH] x86/mce: Provide sysfs interface to show CMCI storm state
Date: Tue, 1 Jun 2021 20:40:34 +0000	[thread overview]
Message-ID: <1cc039a15b4248e1a625dbb6fc275169@intel.com> (raw)
In-Reply-To: <YLaaLws+4FEHOqQs@zn.tnic>

> But I'm unclear as to what this whole use case is. The very first
> "Scripts that process error logs" already sounds like a bad idea - I'd
> expect userspace consumers to open the trace_mce_record() and get the
> MCE records from there. And in that case CMCI storm shouldn't matter...

I think the problem is knowing that many errors are being missed because
of the switch to poll mode. All methods to track errors, including the trace_mce_record()
technique are equally affected by missed errors.

But maybe Chris can better describe what the problem is ...

-Tony

  reply	other threads:[~2021-06-01 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 20:05 [RFC PATCH] x86/mce: Provide sysfs interface to show CMCI storm state Tony Luck
2021-06-01 20:35 ` Borislav Petkov
2021-06-01 20:40   ` Luck, Tony [this message]
2021-06-03 22:48     ` BeSerra, Christopher
2021-06-04  9:16       ` Borislav Petkov

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=1cc039a15b4248e1a625dbb6fc275169@intel.com \
    --to=tony.luck@intel.com \
    --cc=beserra@amazon.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.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