From: Sean Christopherson <seanjc@google.com>
To: 张巍 <zhang_wei@open-hieco.net>
Cc: kvm <kvm@vger.kernel.org>, pbonzini <pbonzini@redhat.com>,
mlevitsk <mlevitsk@redhat.com>, naveen <naveen@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] KVM: SVM: Disable AVIC IPI virtualization on Hygon Family 18h (erratum #1235)
Date: Tue, 26 May 2026 12:14:54 -0700 [thread overview]
Message-ID: <ahXxLup2MZkyli1W@google.com> (raw)
In-Reply-To: <b4dd2e22-2364-40ed-a06f-4082adb309d1.zhang_wei@open-hieco.net>
On Mon, May 25, 2026, 张巍 wrote:
> On Fri, May 22, 2026, Sean Christopherson wrote:
> > IIUC, family 18h is carved out entirely for Hygon, correct? I.e.
> > there's no risk of disabling IPI virtualization on unaffected AMD CPUs?
>
> Yes, that is my understanding.
>
> The original Hygon enablement [1] uses Family 18h together with the
> HygonGenuine vendor ID to distinguish Hygon Dhyana from AMD Family 17h,
> and explicitly states that only Hygon is expected to use Family 18h. So
> this should not affect unaffected AMD CPUs.
>
> I can add an X86_VENDOR_HYGON check too if you prefer making the
> dependency explicit.
No need, I just wanted to double check. And this is already in Linus' tree,
commit 9a12fa5213cf ("KVM: SVM: Disable AVIC IPI virtualization on Hygon Family
18h (erratum #1235)"), so what I would have preferred is irrelevant :-)
Thanks for the follow-up!
prev parent reply other threads:[~2026-05-26 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 4:00 [PATCH] KVM: SVM: Disable AVIC IPI virtualization on Hygon Family 18h (erratum #1235) Tina Zhang
2026-05-22 12:56 ` Sean Christopherson
2026-05-25 3:58 ` 张巍
2026-05-26 19:14 ` Sean Christopherson [this message]
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=ahXxLup2MZkyli1W@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=naveen@kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=zhang_wei@open-hieco.net \
/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