public inbox for kvm@vger.kernel.org
 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: Misc changes for 6.10
Date: Fri, 10 May 2024 16:50:47 -0700	[thread overview]
Message-ID: <20240510235055.2811352-3-seanjc@google.com> (raw)
In-Reply-To: <20240510235055.2811352-1-seanjc@google.com>

The max mappable GPA changes are the most notable, though unless we really
botched the KVM implementation, they should be old news for you.

The other mildly interesting change is a fix for KVM's handling of userspace
writes to immutable feature MSRs.  The seemingly good idea of simply ignoring
the writes, e.g. to avoid a problematic/useless PMU refresh, neglected to
consider the fact that access to the MSR might be disallowed.  E.g. the VMX
MSRs are off limits if nested support is disabled.

The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:

  Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-misc-6.10

for you to fetch changes up to 51937f2aae186e335175dde78279aaf0cb5e72ae:

  KVM: x86: Remove VT-d mention in posted interrupt tracepoint (2024-05-02 07:54:14 -0700)

----------------------------------------------------------------
KVM x86 misc changes for 6.10:

 - Advertise the max mappable GPA in the "guest MAXPHYADDR" CPUID field, which
   is unused by hardware, so that KVM can communicate its inability to map GPAs
   that set bits 51:48 due to lack of 5-level paging.  Guest firmware is
   expected to use the information to safely remap BARs in the uppermost GPA
   space, i.e to avoid placing a BAR at a legal, but unmappable, GPA.

 - Use vfree() instead of kvfree() for allocations that always use vcalloc()
   or __vcalloc().

 - Don't completely ignore same-value writes to immutable feature MSRs, as
   doing so results in KVM failing to reject accesses to MSR that aren't
   supposed to exist given the vCPU model and/or KVM configuration.

 - Don't mark APICv as being inhibited due to ABSENT if APICv is disabled
   KVM-wide to avoid confusing debuggers (KVM will never bother clearing the
   ABSENT inhibit, even if userspace enables in-kernel local APIC).

----------------------------------------------------------------
Alejandro Jimenez (2):
      KVM: x86: Only set APICV_INHIBIT_REASON_ABSENT if APICv is enabled
      KVM: x86: Remove VT-d mention in posted interrupt tracepoint

Gerd Hoffmann (2):
      KVM: x86: Don't advertise guest.MAXPHYADDR as host.MAXPHYADDR in CPUID
      KVM: x86: Advertise max mappable GPA in CPUID.0x80000008.GuestPhysBits

Li RongQing (1):
      KVM: Use vfree for memory allocated by vcalloc()/__vcalloc()

Sean Christopherson (1):
      KVM: x86: Allow, don't ignore, same-value writes to immutable MSRs

 arch/x86/kvm/cpuid.c          | 41 +++++++++++++++++++++++++++++++----------
 arch/x86/kvm/mmu.h            |  2 ++
 arch/x86/kvm/mmu/mmu.c        |  5 +++++
 arch/x86/kvm/mmu/page_track.c |  2 +-
 arch/x86/kvm/trace.h          |  4 ++--
 arch/x86/kvm/x86.c            | 28 +++++++++++-----------------
 virt/kvm/kvm_main.c           |  2 +-
 7 files changed, 53 insertions(+), 31 deletions(-)

  parent reply	other threads:[~2024-05-10 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 23:50 KVM: x86 pull requests for 6.10 Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Common changes " Sean Christopherson
2024-05-10 23:50 ` Sean Christopherson [this message]
2024-05-10 23:50 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests cleanups and fixes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests "tree"-wide changes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2024-05-12  7:19 ` KVM: x86 pull requests " Paolo Bonzini

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=20240510235055.2811352-3-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