From: Joao Martins <joao.m.martins@oracle.com>
To: John Allen <john.allen@amd.com>,
pbonzini@redhat.com, william.roche@oracle.com
Cc: yazen.ghannam@amd.com, michael.roth@amd.com, babu.moger@amd.com,
richard.henderson@linaro.org, eduardo@habkost.net,
qemu-devel@nongnu.org, "peterx@redhat.com" <peterx@redhat.com>
Subject: Re: [PATCH v4 0/3] Fix MCE handling on AMD hosts
Date: Wed, 7 Feb 2024 11:21:05 +0000 [thread overview]
Message-ID: <afc99063-1916-4a0c-a763-f515a4595e73@oracle.com> (raw)
In-Reply-To: <20230912211824.90952-1-john.allen@amd.com>
On 12/09/2023 22:18, John Allen wrote:
> In the event that a guest process attempts to access memory that has
> been poisoned in response to a deferred uncorrected MCE, an AMD system
> will currently generate a SIGBUS error which will result in the entire
> guest being shutdown. Ideally, we only want to kill the guest process
> that accessed poisoned memory in this case.
>
> This support has been included in qemu for Intel hosts for a long time,
> but there are a couple of changes needed for AMD hosts. First, we will
> need to expose the SUCCOR cpuid bit to guests. Second, we need to modify
> the MCE injection code to avoid Intel specific behavior when we are
> running on an AMD host.
>
Is there any update with respect to this series?
John's series should fix MCE injection on AMD; as today it is just crashing the
guest (sadly) when an MCE happens in the hypervisor.
William, Paolo, I think the sort-of-dependency(?) of this where we block
migration if there was a poisoned page on is already in Peter's migration
tree[1] (CC'ed). So perhaps this series just needs John to resend it given that
it's been a couple months since v4?
[1]
https://lore.kernel.org/qemu-devel/20240130190640.139364-2-william.roche@oracle.com/
> v2:
> - Add "succor" feature word.
> - Add case to kvm_arch_get_supported_cpuid for the SUCCOR feature.
>
> v3:
> - Reorder series. Only enable SUCCOR after bugs have been fixed.
> - Introduce new patch ignoring AO errors.
>
> v4:
> - Remove redundant check for AO errors.
>
> John Allen (2):
> i386: Fix MCE support for AMD hosts
> i386: Add support for SUCCOR feature
>
> William Roche (1):
> i386: Explicitly ignore unsupported BUS_MCEERR_AO MCE on AMD guest
>
> target/i386/cpu.c | 18 +++++++++++++++++-
> target/i386/cpu.h | 4 ++++
> target/i386/helper.c | 4 ++++
> target/i386/kvm/kvm.c | 28 ++++++++++++++++++++--------
> 4 files changed, 45 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2024-02-07 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:18 [PATCH v4 0/3] Fix MCE handling on AMD hosts John Allen
2023-09-12 21:18 ` [PATCH v4 1/3] i386: Fix MCE support for " John Allen
2023-09-12 21:18 ` [PATCH v4 2/3] i386: Explicitly ignore unsupported BUS_MCEERR_AO MCE on AMD guest John Allen
2023-09-13 3:22 ` Gupta, Pankaj
2023-09-18 22:00 ` William Roche
2023-09-20 11:13 ` Joao Martins
2023-09-21 17:41 ` Yazen Ghannam
2023-09-22 8:36 ` William Roche
2023-09-22 14:30 ` Yazen Ghannam
2023-09-22 16:18 ` William Roche
2023-10-13 15:41 ` William Roche
2023-09-12 21:18 ` [PATCH v4 3/3] i386: Add support for SUCCOR feature John Allen
2024-02-07 11:21 ` Joao Martins [this message]
2024-02-20 17:27 ` [PATCH v4 0/3] Fix MCE handling on AMD hosts John Allen
2024-02-21 11:42 ` Joao Martins
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=afc99063-1916-4a0c-a763-f515a4595e73@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=babu.moger@amd.com \
--cc=eduardo@habkost.net \
--cc=john.allen@amd.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=william.roche@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).