All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosry@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, Kevin Cheng <chengkev@google.com>,
	 andrew.jones@linux.dev, thuth@redhat.com, pbonzini@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 0/2] x86/svm: Add testing for L1 intercept bug
Date: Wed, 27 May 2026 22:00:18 +0000	[thread overview]
Message-ID: <ahdpRGN3Rctg6MrH@google.com> (raw)
In-Reply-To: <177989663546.4071483.13324448017637391219.b4-ty@google.com>

On Wed, May 27, 2026 at 10:49:06AM -0700, Sean Christopherson wrote:
> On Wed, 24 Dec 2025 01:43:22 +0000, Kevin Cheng wrote:
> > If a feature is not advertised to L1, L1 intercepts for instructions
> > controlled by this feature should be ignored. Currently, the added test
> > fails due to a bug in nested vm exit handling where vmcb12 intercepts
> > are checked before vmcb02 intercepts, causing the #UD exception to never
> > be injected into L2 if the L1 intercept is set. This is fixed in [0]
> > 
> > The first patch just adds the missing intercepts needed for testing and
> > restructures the vmcb_control_area struct to make adding the missing
> > intercepts less ugly. The second patch adds the test which disables all
> > relevant features that have available instruction intercepts, and checks
> > that the #UD exception is correctly delivered despite the L1 intercept
> > being set.
> > 
> > [...]
> 
> Applied to kvm-x86 next, even though the SKINIT test fails on the Turin system
> available to me.  AIUI, there's a ucode bug or something for pre-production
> hardware?
> 
> Anyways, I mention that because if others see failures, then we'll probably
> need to figure out a way to automatically skip the SKINIT test (or maybe eat
> the #GP and treat it as XFAIL?).
> 
> [1/2] x86/svm: Add missing svm intercepts
>       https://github.com/kvm-x86/kvm-unit-tests/commit/8322ddeda22b

So I believe there is no need to split that patch anymore since you
already applied it, right?

Also, I think there was a newer version of this series:
https://lore.kernel.org/kvm/20260312204009.3168871-1-chengkev@google.com/

> [2/2] x86/svm: Add unsupported instruction intercept test
>       https://github.com/kvm-x86/kvm-unit-tests/commit/7586f98f809e
> 
> --
> https://github.com/kvm-x86/kvm-unit-tests/tree/next

      reply	other threads:[~2026-05-27 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24  1:43 [kvm-unit-tests PATCH v3 0/2] x86/svm: Add testing for L1 intercept bug Kevin Cheng
2025-12-24  1:43 ` [kvm-unit-tests PATCH v3 1/2] x86/svm: Add missing svm intercepts Kevin Cheng
2026-05-20 14:57   ` Sean Christopherson
2026-05-20 14:59     ` Paolo Bonzini
2025-12-24  1:43 ` [kvm-unit-tests PATCH v3 2/2] x86/svm: Add unsupported instruction intercept test Kevin Cheng
2026-05-27 17:49 ` [kvm-unit-tests PATCH v3 0/2] x86/svm: Add testing for L1 intercept bug Sean Christopherson
2026-05-27 22:00   ` Yosry Ahmed [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=ahdpRGN3Rctg6MrH@google.com \
    --to=yosry@kernel.org \
    --cc=andrew.jones@linux.dev \
    --cc=chengkev@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.