From: Jim Mattson <jmattson@google.com>
To: Yosry Ahmed <yosry.ahmed@linux.dev>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jim Mattson <jmattson@google.com>
Subject: [PATCH v2 0/2] KVM: SVM: GIF and EFER.SVME are independent
Date: Thu, 9 Oct 2025 15:31:32 -0700 [thread overview]
Message-ID: <20251009223153.3344555-1-jmattson@google.com> (raw)
Clearing EFER.SVME is not architected to set GIF, so GIF may be clear
even when EFER.SVME is clear.
This is covered in the discussion at
https://lore.kernel.org/all/5b8787b8-16e9-13dc-7fca-0dc441d673f9@citrix.com/.
v2:
- Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0
v1: https://lore.kernel.org/kvm/20251007224405.1914008-1-jmattson@google.com/
Jim Mattson (2):
KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0
KVM: SVM: Don't set GIF when clearing EFER.SVME
arch/x86/kvm/svm/nested.c | 4 ++--
arch/x86/kvm/svm/svm.c | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.51.0.740.g6adb054d12-goog
next reply other threads:[~2025-10-09 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 22:31 Jim Mattson [this message]
2025-10-09 22:31 ` [PATCH v2 1/2] KVM: SVM: Allow KVM_SET_NESTED_STATE to clear GIF when SVME==0 Jim Mattson
2025-10-09 23:24 ` Yosry Ahmed
2025-10-09 22:31 ` [PATCH v2 2/2] KVM: SVM: Don't set GIF when clearing EFER.SVME Jim Mattson
2025-10-13 22:33 ` Sean Christopherson
2025-10-14 20:51 ` Jim Mattson
2025-10-14 21:18 ` Sean Christopherson
2025-10-14 21:31 ` Jim Mattson
2025-10-14 22:07 ` Sean Christopherson
2025-10-14 22:58 ` Jim Mattson
2025-10-17 21:56 ` Sean Christopherson
2025-11-11 0:26 ` 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=20251009223153.3344555-1-jmattson@google.com \
--to=jmattson@google.com \
--cc=bp@alien8.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=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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