From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: SVM changes for 6.12
Date: Fri, 13 Sep 2024 18:13:47 -0700 [thread overview]
Message-ID: <20240914011348.2558415-7-seanjc@google.com> (raw)
In-Reply-To: <20240914011348.2558415-1-seanjc@google.com>
I got nothing clever or interesting to say for this one.
The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:
Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-6.12
for you to fetch changes up to 4440337af4d415c8abf8b9b0e10c79b7518e6e3c:
KVM: SVM: let alternatives handle the cases when RSB filling is required (2024-09-10 10:27:53 -0700)
----------------------------------------------------------------
KVM SVM changes for 6.12:
- Don't stuff the RSB after VM-Exit when RETPOLINE=y and AutoIBRS is enabled,
i.e. when the CPU has already flushed the RSB.
- Trace the per-CPU host save area as a VMCB pointer to improve readability
and cleanup the retrieval of the SEV-ES host save area.
- Remove unnecessary accounting of temporary nested VMCB related allocations.
----------------------------------------------------------------
Amit Shah (1):
KVM: SVM: let alternatives handle the cases when RSB filling is required
Sean Christopherson (3):
KVM: SVM: Add a helper to convert a SME-aware PA back to a struct page
KVM: SVM: Add host SEV-ES save area structure into VMCB via a union
KVM: SVM: Track the per-CPU host save area as a VMCB pointer
Yongqiang Liu (1):
KVM: SVM: Remove unnecessary GFP_KERNEL_ACCOUNT in svm_set_nested_state()
arch/x86/include/asm/svm.h | 20 +++++++++++++++-----
arch/x86/kvm/svm/nested.c | 4 ++--
arch/x86/kvm/svm/svm.c | 24 ++++++++++++------------
arch/x86/kvm/svm/svm.h | 18 ++++++++++++++++--
arch/x86/kvm/svm/vmenter.S | 8 ++------
5 files changed, 47 insertions(+), 27 deletions(-)
next prev parent reply other threads:[~2024-09-14 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 1:13 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2024-09-14 1:13 ` [GIT PULL] KVM: Common changes " Sean Christopherson
2024-09-14 13:35 ` Paolo Bonzini
2024-09-14 1:13 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-09-14 1:13 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-09-14 13:50 ` Paolo Bonzini
2024-09-14 1:13 ` [GIT PULL] KVM: x86: VMX and PAT MSRs cleanup Sean Christopherson
2024-09-14 1:13 ` [GIT PULL] KVM: Selftests changes for 6.12 Sean Christopherson
2024-09-14 1:13 ` Sean Christopherson [this message]
2024-09-14 1:13 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2024-09-14 14:54 ` [GIT PULL] KVM: x86 pull requests " Paolo Bonzini
2024-09-15 6:32 ` Paolo Bonzini
2024-09-16 18:24 ` Sean Christopherson
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=20240914011348.2558415-7-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®