From: Aristeu Rozanski <aris@ruivo.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"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, 5 Jun 2023 16:10:49 -0400 [thread overview]
Message-ID: <20230605201049.GP4090740@cathedrallabs.org> (raw)
In-Reply-To: <20230605193000.GDZH43uFhBmQfSO+9D@fat_crate.local>
On Mon, Jun 05, 2023 at 09:30:00PM +0200, Borislav Petkov wrote:
> Btw, why was that spinlock raw?
Didn't want RT code thinking it could preempt us but it doesn't really
matter.
--
Aristeu
next prev parent reply other threads:[~2023-06-05 20:11 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
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 [this message]
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=20230605201049.GP4090740@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