Linux EDAC development
 help / color / mirror / Atom feed
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>,
	"aris@redhat.com" <aris@redhat.com>
Subject: Re: [RFC PATCH] mce: prevent concurrent polling of MCE events
Date: Tue, 17 Jan 2023 13:58:15 -0500	[thread overview]
Message-ID: <Y8bvxxuf7XIPwEFZ@cathedrallabs.org> (raw)
In-Reply-To: <IA1PR11MB607672430721985FD208F00BFCC69@IA1PR11MB6076.namprd11.prod.outlook.com>

On Tue, Jan 17, 2023 at 06:54:02PM +0000, Luck, Tony wrote:
> > Yes, but could change the patch to include mce_available() into the
> > protection of the lock. It should cleared once machine_check_poll() clears
> > the bank state, no?
> 
> Which machines are showing this problem? Most modern systems support
> CMCI. So I'm thinking that this case shows up because the sysadmin booted
> with "mce=no_cmc;". In that case I don't think mce_available() check would
> change anything.

That is correct, ignore what I said.

-- 
Aristeu


  reply	other threads:[~2023-01-17 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 20:01 [RFC PATCH] mce: prevent concurrent polling of MCE events Aristeu Rozanski
2023-01-17 17:42 ` Luck, Tony
2023-01-17 18:44   ` Aristeu Rozanski
2023-01-17 18:54     ` Luck, Tony
2023-01-17 18:58       ` Aristeu Rozanski [this message]
2023-04-28 15:51   ` Aristeu Rozanski
2023-04-28 16:43     ` Luck, Tony
2023-05-11 23:38       ` Tony Luck
2023-05-12 17:32         ` Aristeu Rozanski
2023-05-12 19:19           ` Luck, Tony

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=Y8bvxxuf7XIPwEFZ@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