From: "“William Roche" <william.roche@oracle.com>
To: yazen.ghannam@amd.com, tony.luck@intel.com, bp@alien8.de,
tglx@kernel.org, mingo@redhat.com, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: John.Allen@amd.com, jane.chu@oracle.com, william.roche@oracle.com
Subject: [PATCH v2 0/1] AMD VM crashing on deferred memory error injection
Date: Wed, 18 Feb 2026 16:30:24 +0000 [thread overview]
Message-ID: <20260218163025.1316501-1-william.roche@oracle.com> (raw)
From: William Roche <william.roche@oracle.com>
Thank you very much Yazen for your review and all the suggestions!
v2 changes:
- Commit title changed to:
x86/mce/amd: Fix VM crash during deferred error handling
- Commit message with capitalized QEMU and KVM as well as the imperative
statement suggested by Yazen
- "CC stable" tag placed after "Signed-off-by"
(The documentation asks for "the sign-off area" without more details)
- blank line added to separate SCMA code block and the update of
MCA_STATUS.
--
After the integration of the following commit:
7cb735d7c0cb x86/mce: Unify AMD DFR handler with MCA Polling
AMD Qemu VM started to crash when dealing with deferred memory error
injection with a stack trace like:
mce: MSR access error: WRMSR to 0xc0002098 (tried to write 0x0000000000000000)
at rIP: 0xffffffff8229894d (mce_wrmsrq+0x1d/0x60)
amd_clear_bank+0x6e/0x70
machine_check_poll+0x228/0x2e0
? __pfx_mce_timer_fn+0x10/0x10
mce_timer_fn+0xb1/0x130
? __pfx_mce_timer_fn+0x10/0x10
call_timer_fn+0x26/0x120
__run_timers+0x202/0x290
run_timer_softirq+0x49/0x100
handle_softirqs+0xeb/0x2c0
__irq_exit_rcu+0xda/0x100
sysvec_apic_timer_interrupt+0x71/0x90
[...]
Kernel panic - not syncing: MCA architectural violation!
See the discussion at:
https://lore.kernel.org/all/48d8e1c8-1eb9-49cc-8de8-78077f29c203@oracle.com/
We identified a problem with SMCA specific registers access from
non-SMCA platforms like a QEMU/KVM machine.
This patch is checkpatch.pl clean.
Unit test of memory error injection works fine with it.
William Roche (1):
x86/mce/amd: Fix VM crash during deferred error handling
arch/x86/kernel/cpu/mce/amd.c | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
--
2.47.3
next reply other threads:[~2026-02-18 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 16:30 “William Roche [this message]
2026-02-18 16:30 ` [PATCH v2 1/1] x86/mce/amd: Fix VM crash during deferred error handling “William Roche
2026-03-12 14:42 ` Borislav Petkov
2026-03-12 15:11 ` William Roche
2026-03-12 16:04 ` Borislav Petkov
2026-03-12 22:44 ` William Roche
2026-03-13 20:10 ` Borislav Petkov
2026-03-16 15:27 ` William Roche
2026-03-13 20:26 ` Yazen Ghannam
2026-03-16 15:26 ` William Roche
2026-03-19 14:25 ` Yazen Ghannam
2026-03-12 14:23 ` [PATCH v2 0/1] AMD VM crashing on deferred memory error injection William Roche
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=20260218163025.1316501-1-william.roche@oracle.com \
--to=william.roche@oracle.com \
--cc=John.Allen@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jane.chu@oracle.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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
all inboxes | Powered by JetHome®