From: Igor Mammedov <imammedo@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, babu.moger@amd.com
Subject: Re: [kvm-unit-tests PATCH] x86/svm: work around Virtual VMLOAD/VMSAVE bug on Naples and Rome
Date: Mon, 18 May 2026 16:40:44 +0200 [thread overview]
Message-ID: <20260518164044.5f06f840@imammedo> (raw)
In-Reply-To: <agsidj11-eY80au1@google.com>
On Mon, 18 May 2026 07:30:14 -0700
Sean Christopherson <seanjc@google.com> wrote:
> On Mon, May 18, 2026, Igor Mammedov wrote:
> > On Fri, 15 May 2026 05:44:37 -0700
> > Sean Christopherson <seanjc@google.com> wrote:
> > > > +static bool has_vls_bug(void)
> > >
> > > Probably need to be more specific, because there appear to be multiple flavors
> > > of vls bugs. :-/
> >
> >
> > would something like this work:
> >
> > -static bool has_vls_bug(void)
> > +/*
> > + * Naples (Fam17h/00-0f) and Rome (Fam17h/30-3f) cause spurious VMEXITs
> > + * on VMLOAD/VMSAVE when the VMCB address falls in [0x78000000, 0x80000000).
> > + */
> > +static bool has_vls_spurious_vmexit_bug(void)
>
> Works for me. Any chance you have a specific erratum number that we could reference?
I'll try to find it. That's also was a reason to cc AMD side, for they probably
know better where/what to look for.
>
prev parent reply other threads:[~2026-05-18 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 11:19 [kvm-unit-tests PATCH] x86/svm: work around Virtual VMLOAD/VMSAVE bug on Naples and Rome Igor Mammedov
2026-05-15 12:44 ` Sean Christopherson
2026-05-18 12:32 ` Igor Mammedov
2026-05-18 14:30 ` Sean Christopherson
2026-05-18 14:40 ` Igor Mammedov [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=20260518164044.5f06f840@imammedo \
--to=imammedo@redhat.com \
--cc=babu.moger@amd.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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