mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.16
Date: Fri, 23 May 2025 09:25:02 -0700	[thread overview]
Message-ID: <20250523162504.3281680-6-seanjc@google.com> (raw)
In-Reply-To: <20250523162504.3281680-1-seanjc@google.com>

A variety of SEV changes, and support for BUS_LOCK_EXIT (Bus Lock Threshold).

The following changes since commit 45eb29140e68ffe8e93a5471006858a018480a45:

  Merge branch 'kvm-fixes-6.15-rc4' into HEAD (2025-04-24 13:39:34 -0400)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-6.16

for you to fetch changes up to 72df72e1c6ddfb6e0c2bce174d5879bc095540c8:

  KVM: selftests: Add test to verify KVM_CAP_X86_BUS_LOCK_EXIT (2025-05-19 11:05:19 -0700)

----------------------------------------------------------------
KVM SVM changes for 6.16:

 - Wait for target vCPU to acknowledge KVM_REQ_UPDATE_PROTECTED_GUEST_STATE to
   fix a race between AP destroy and VMRUN.

 - Decrypt and dump the VMSA in dump_vmcb() if debugging enabled for the VM.

 - Add support for ALLOWED_SEV_FEATURES.

 - Add #VMGEXIT to the set of handlers special cased for CONFIG_RETPOLINE=y.

 - Treat DEBUGCTL[5:2] as reserved to pave the way for virtualizing features
   that utilize those bits.

 - Don't account temporary allocations in sev_send_update_data().

 - Add support for KVM_CAP_X86_BUS_LOCK_EXIT on SVM, via Bus Lock Threshold.

----------------------------------------------------------------
Kim Phillips (1):
      KVM: SEV: Configure "ALLOWED_SEV_FEATURES" VMCB Field

Kishon Vijay Abraham I (1):
      x86/cpufeatures: Add "Allowed SEV Features" Feature

Manali Shukla (3):
      KVM: x86: Make kvm_pio_request.linear_rip a common field for user exits
      x86/cpufeatures: Add CPUID feature bit for the Bus Lock Threshold
      KVM: SVM: Add support for KVM_CAP_X86_BUS_LOCK_EXIT on SVM CPUs

Nikunj A Dadhania (2):
      KVM: SVM: Add architectural definitions/assets for Bus Lock Threshold
      KVM: selftests: Add test to verify KVM_CAP_X86_BUS_LOCK_EXIT

Peng Hao (2):
      KVM: SVM: avoid frequency indirect calls
      x86/sev: Remove unnecessary GFP_KERNEL_ACCOUNT for temporary variables

Sean Christopherson (1):
      KVM: SVM: Treat DEBUGCTL[5:2] as reserved

Tom Lendacky (6):
      KVM: SVM: Fix SNP AP destroy race with VMRUN
      KVM: SVM: Decrypt SEV VMSA in dump_vmcb() if debugging is enabled
      KVM: SVM: Dump guest register state in dump_vmcb()
      KVM: SVM: Add the type of VM for which the VMCB/VMSA is being dumped
      KVM: SVM: Include the vCPU ID when dumping a VMCB
      KVM: SVM: Add a mutex to dump_vmcb() to prevent concurrent output

 Documentation/virt/kvm/api.rst                     |   5 +
 arch/x86/include/asm/cpufeatures.h                 |   2 +
 arch/x86/include/asm/kvm_host.h                    |   5 +-
 arch/x86/include/asm/svm.h                         |  10 +-
 arch/x86/include/uapi/asm/svm.h                    |   2 +
 arch/x86/kvm/svm/nested.c                          |  34 ++++++
 arch/x86/kvm/svm/sev.c                             | 113 ++++++++++++++++-
 arch/x86/kvm/svm/svm.c                             | 135 +++++++++++++++++++--
 arch/x86/kvm/svm/svm.h                             |  12 ++
 arch/x86/kvm/x86.c                                 |   8 +-
 include/linux/kvm_host.h                           |  19 ++-
 tools/testing/selftests/kvm/Makefile.kvm           |   1 +
 tools/testing/selftests/kvm/x86/kvm_buslock_test.c | 135 +++++++++++++++++++++
 virt/kvm/kvm_main.c                                |  19 ++-
 14 files changed, 469 insertions(+), 31 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/x86/kvm_buslock_test.c

  parent reply	other threads:[~2025-05-23 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 16:24 [GIT PULL] KVM: x86: Changes " Sean Christopherson
2025-05-23 16:24 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-05-23 16:24 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2025-05-23 16:25 ` [GIT PULL] KVM: x86: Posted Interrupt PIR " Sean Christopherson
2025-05-23 16:25 ` [GIT PULL] KVM: selftests " Sean Christopherson
2025-05-23 16:25 ` Sean Christopherson [this message]
2025-05-23 16:25 ` [GIT PULL] KVM: x86: VMX " 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=20250523162504.3281680-6-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®