public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] KVM: nSVM: Do not track EFER.SVME toggling in guest mode
Date: Wed, 4 Feb 2026 18:10:36 -0800	[thread overview]
Message-ID: <aYP8HGQrj2aW6NGJ@google.com> (raw)
In-Reply-To: <byogsjz2vljtzvr7ar4wefm3mrzqxboujz2yugsszgrtkluyks@phifb333vw45>

On Wed, Feb 04, 2026, Yosry Ahmed wrote:
> On Wed, Feb 04, 2026 at 01:15:45PM -0800, Sean Christopherson wrote:
> > All that said, I agree that pulling the rug out from under the VM is a terrible
> > experience.  What if we throw a triple fault at the vCPU so that L1 gets an
> > immediate SHUTDOWN (not a VM-Exit, a SHUTDOWN of the L1 vCPU), instead of running
> > random garbage from L2?
> 
> I am fine with this too, anything is better than pulling the rug. I will
> send a v2 and probably drop patch 1 (unless you prefer that we keep it).

Drop it, otherwise we'll probably end up wasting several days bikeshedding the
name.

  reply	other threads:[~2026-02-05  2:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  2:07 [PATCH 0/3] KVM: nSVM: Stop tracking EFER.SVME in guest mode Yosry Ahmed
2026-01-30  2:07 ` [PATCH 1/3] KVM: SVM: Refactor EFER.SVME switching logic out of svm_set_efer() Yosry Ahmed
2026-02-04 18:49   ` Sean Christopherson
2026-01-30  2:07 ` [PATCH 2/3] KVM: nSVM: Do not track EFER.SVME toggling in guest mode Yosry Ahmed
2026-02-04 21:15   ` Sean Christopherson
2026-02-04 23:30     ` Yosry Ahmed
2026-02-05  2:10       ` Sean Christopherson [this message]
2026-01-30  2:07 ` [PATCH 3/3] KVM: selftests: Add a test for L2 toggling EFER.SVME Yosry Ahmed

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=aYP8HGQrj2aW6NGJ@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yosry.ahmed@linux.dev \
    /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