From: Aristeu Rozanski <aris@ruivo.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Aristeu Rozanski <aris@redhat.com>
Subject: Re: [PATCH] mce: prevent concurrent polling of MCE events
Date: Mon, 15 May 2023 16:32:20 -0400 [thread overview]
Message-ID: <20230515203220.GE4090740@cathedrallabs.org> (raw)
In-Reply-To: <SJ1PR11MB6083A169CC5FD7057338027AFC789@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Mon, May 15, 2023 at 08:27:19PM +0000, Luck, Tony wrote:
> If CMCI storms are their problem ... perhaps this is an answer:
>
> https://lore.kernel.org/all/20230411173841.70491-1-tony.luck@intel.com/
Apparently they're disabling CMCI for CE and UCNA events when OS-first is
enabled for two entire lines of products. So there might be more behind
this than I suspected. I just sent a message to their engineers to find out
what's going on.
Now on the CMCI storm mitigation, wouldn't a system that got a storm be
subject to this same issue of duplicated events since it switches to polling?
--
Aristeu
next prev parent reply other threads:[~2023-05-15 20:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:32 [PATCH] mce: prevent concurrent polling of MCE events Aristeu Rozanski
2023-05-15 14:52 ` Borislav Petkov
2023-05-15 17:18 ` Luck, Tony
2023-05-15 18:30 ` Borislav Petkov
2023-05-15 19:08 ` Luck, Tony
2023-05-15 19:44 ` Borislav Petkov
2023-05-15 20:07 ` Luck, Tony
2023-05-15 20:20 ` Aristeu Rozanski
2023-05-15 20:27 ` Luck, Tony
2023-05-15 20:32 ` Aristeu Rozanski [this message]
2023-05-15 20:40 ` Luck, Tony
2023-05-16 17:08 ` Borislav Petkov
2023-05-23 14:15 ` Aristeu Rozanski
2023-06-04 16:04 ` Aristeu Rozanski
2023-06-05 15:33 ` Luck, Tony
2023-06-05 17:41 ` Borislav Petkov
2023-06-05 17:58 ` Luck, Tony
2023-06-05 19:30 ` Borislav Petkov
2023-06-05 19:37 ` Luck, Tony
2023-06-05 19:43 ` Borislav Petkov
2023-06-05 20:10 ` Aristeu Rozanski
2023-06-05 20:33 ` Aristeu Rozanski
2023-06-05 20:56 ` Borislav Petkov
2023-06-05 21:01 ` Aristeu Rozanski
2023-06-05 21:06 ` Borislav Petkov
2023-06-05 21:29 ` Luck, Tony
2023-06-05 21:58 ` Aristeu Rozanski
2023-06-06 8:25 ` Borislav Petkov
2023-06-06 14:00 ` Aristeu Rozanski
2023-06-06 14:08 ` Borislav Petkov
2023-06-09 0:26 ` Luck, Tony
2023-06-09 10:17 ` Borislav Petkov
2023-06-09 15:00 ` Yazen Ghannam
2023-06-09 15:24 ` Luck, Tony
2023-06-09 16:00 ` Yazen Ghannam
2023-06-09 15:59 ` Aristeu Rozanski
2023-06-05 19:08 ` Aristeu Rozanski
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=20230515203220.GE4090740@cathedrallabs.org \
--to=aris@ruivo.org \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--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