public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris@ruivo.org>
To: linux-edac@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
	"Luck, Tony" <tony.luck@intel.com>,
	Aristeu Rozanski <aris@redhat.com>
Subject: [PATCH] mce: prevent concurrent polling of MCE events
Date: Mon, 15 May 2023 10:32:25 -0400	[thread overview]
Message-ID: <20230515143225.GC4090740@cathedrallabs.org> (raw)

Error injection in modern HP machines with CMCI disabled will cause the
injected MCE to be found only by polling. Because these newer machines have a
big number of CPUs per package, it makes a lot more likely for multiple
CPUs polling IMC registers (that are shared in the same package) at same time,
causing multiple reports of the same MCE.

Signed-off-by: Aristeu Rozanski <aris@ruivo.org>
Reviewed-by: Tony Luck <tony.luck@intel.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org

--- a/arch/x86/kernel/cpu/mce/core.c
+++ b/arch/x86/kernel/cpu/mce/core.c
@@ -1597,6 +1597,7 @@ static unsigned long check_interval = INITIAL_CHECK_INTERVAL;
 
 static DEFINE_PER_CPU(unsigned long, mce_next_interval); /* in jiffies */
 static DEFINE_PER_CPU(struct timer_list, mce_timer);
+static DEFINE_RAW_SPINLOCK(timer_fn_lock);
 
 static unsigned long mce_adjust_timer_default(unsigned long interval)
 {
@@ -1628,7 +1629,9 @@ static void mce_timer_fn(struct timer_list *t)
 	iv = __this_cpu_read(mce_next_interval);
 
 	if (mce_available(this_cpu_ptr(&cpu_info))) {
+		raw_spin_lock(&timer_fn_lock);
 		machine_check_poll(0, this_cpu_ptr(&mce_poll_banks));
+		raw_spin_unlock(&timer_fn_lock);
 
 		if (mce_intel_cmci_poll()) {
 			iv = mce_adjust_timer(iv);


             reply	other threads:[~2023-05-15 14:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 14:32 Aristeu Rozanski [this message]
2023-05-15 14:52 ` [PATCH] mce: prevent concurrent polling of MCE events 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
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=20230515143225.GC4090740@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