From: Thomas Gleixner <tglx@linutronix.de>
To: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>,
Dave Hansen <dave.hansen@intel.com>,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, keescook@chromium.org,
tony.luck@intel.com, gpiccoli@igalia.com, mat.jonczyk@o2.pl,
rdunlap@infradead.org, alexandre.belloni@bootlin.com,
mario.limonciello@amd.com, yaolu@kylinos.cn, bhelgaas@google.com,
justinstitt@google.com, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Cc: CobeChen@zhaoxin.com, TimGuo@zhaoxin.com, LeoLiu-oc@zhaoxin.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86/hpet: Read HPET directly if panic in progress
Date: Wed, 29 May 2024 09:44:30 +0200 [thread overview]
Message-ID: <87ikyx9i5d.ffs@tglx> (raw)
In-Reply-To: <2553dd17-f763-4894-89b7-5f76c03d3a37@zhaoxin.com>
On Wed, May 29 2024 at 12:39, Tony W Wang-oc wrote:
> printk deadlock will happened at #A because in_nmi() evaluates to false
> on CPU B and CPU B do not enter the panic() AT #A.
>
> Update user space MCE handler to NMI class context is preferred?
No.
next prev parent reply other threads:[~2024-05-29 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:38 [PATCH] x86/hpet: Read HPET directly if panic in progress Tony W Wang-oc
2024-05-28 14:18 ` Dave Hansen
2024-05-28 22:12 ` Thomas Gleixner
2024-05-28 23:22 ` Linus Torvalds
2024-05-29 7:42 ` Thomas Gleixner
2024-06-05 6:23 ` Tony W Wang-oc
2024-06-05 9:36 ` Borislav Petkov
2024-06-05 10:10 ` Tony W Wang-oc
2024-06-05 11:33 ` Borislav Petkov
2024-06-05 12:02 ` Tony W Wang-oc
2024-06-05 15:51 ` Luck, Tony
2024-06-06 8:44 ` Tony W Wang-oc
2024-06-06 17:00 ` Luck, Tony
2024-05-29 4:39 ` Tony W Wang-oc
2024-05-29 6:44 ` Tony W Wang-oc
2024-05-29 7:45 ` Thomas Gleixner
2024-05-29 8:15 ` Tony W Wang-oc
2024-05-29 7:44 ` Thomas Gleixner [this message]
2024-07-01 11:09 ` Tony W Wang-oc
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=87ikyx9i5d.ffs@tglx \
--to=tglx@linutronix.de \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gpiccoli@igalia.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mat.jonczyk@o2.pl \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yaolu@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.