From: Sean Christopherson <seanjc@google.com>
To: "Sean Christopherson" <seanjc@google.com>,
kvm@vger.kernel.org, pbonzini@redhat.com,
"Carlos López" <clopez@suse.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@kernel.org,
mingo@redhat.com, dave.hansen@linux.intel.com, hpa@zytor.com
Subject: Re: [PATCH v3 0/2] KVM: x86: MCE fixes
Date: Tue, 14 Jul 2026 11:41:19 -0700 [thread overview]
Message-ID: <178405244468.3109537.2871662581077641578.b4-ty@google.com> (raw)
In-Reply-To: <20260609131856.2562222-2-clopez@suse.de>
On Tue, 09 Jun 2026 15:18:54 +0200, Carlos López wrote:
> These two patches are somewhat unrelated, but patch 2 came out of
> Sean's suggestions from reviewing the first patch (see [1]). Patch 1 is
> unchanged.
>
> v3:
> * Address Sashiko's review. While incorrect in pointing out MCIP's
> role, it was partially correct in the sense that the MCE logging
> rules were still not fully compliant to the SDM.
>
> [...]
Applied patch 1 to kvm-x86 misc so it doesn't get waylaid any longer. I'll
respond to patch 2 at some point (hopefully today, but it might not be until
next week).
[1/2] KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce()
https://github.com/kvm-x86/linux/commit/249f9be58c7f
--
https://github.com/kvm-x86/linux/tree/next
next prev parent reply other threads:[~2026-07-14 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 13:18 Carlos López
2026-06-09 13:18 ` [PATCH v3 1/2] KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() Carlos López
2026-06-09 13:18 ` [PATCH v3 2/2] KVM: x86: Fix MCE logging rules for KVM_X86_SET_MCE Carlos López
2026-07-14 18:41 ` Sean Christopherson [this message]
2026-10-27 14:18 ` [PATCH v3 0/2] KVM: x86: MCE fixes Carlos López
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=178405244468.3109537.2871662581077641578.b4-ty@google.com \
--to=seanjc@google.com \
--cc=clopez@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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®