<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/Documentation/virt/kvm, branch master</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>Merge tag 'kvm-s390-next-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD</title>
<updated>2026-10-19T13:11:58+00:00</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2026-10-19T13:11:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=814607cd40df80d5727957adaa857e0feca43497'/>
<id>814607cd40df80d5727957adaa857e0feca43497</id>
<content type='text'>
KVM: s390: Changes for 7.4

- rework page allocation for secure guest variable storage
- selftests
- documentation
- replace get_zeroed_page with kzalloc
- fix floating interrupt inject for corner cases
- initial arm64 on s390 support

This also contains the patch
"arm64: Use proper include variant"
as a build fix. It is also part of the arm tree.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
KVM: s390: Changes for 7.4

- rework page allocation for secure guest variable storage
- selftests
- documentation
- replace get_zeroed_page with kzalloc
- fix floating interrupt inject for corner cases
- initial arm64 on s390 support

This also contains the patch
"arm64: Use proper include variant"
as a build fix. It is also part of the arm tree.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'kvm-x86-misc-7.4' of https://github.com/kvm-x86/linux into HEAD</title>
<updated>2026-10-16T07:50:20+00:00</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2026-10-16T07:50:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=7213f4e515354c398276689e82cbac011e678646'/>
<id>7213f4e515354c398276689e82cbac011e678646</id>
<content type='text'>
KVM x86 misc changes for 7.4

 - Mask off the address space ID when checking for illegal usage of
   kvm_set_internal_memslot() to prevent false negatives on the sanity check.

 - Explicitly zero reserved flags when delivering a SynIC message to avoid
   leaking a byte of stack information to the guest.

 - Rework TDX's handling of the canonical MMU root level to not rely on
   userspace to fill CPUID correctly, as doing so lets userspace trivially
   trigger a KVM_BUG_ON().

 - Reject KVM_SET_NESTED_STATE if userspace "restores" L1 with EFER.LMA=1 &amp;&amp;
   EFER.LME=0, which confuses KVM into trying to configure an 64-bit MMU
   without PAE.

 - Ignore EFER.LMA (clear it from KVM's cached save state) if EFER.LME=0 when
   preparing L2 state, to fix another way to confuse KVM's MMU (and because
   real hardware also ignores EFER.LMA).

 - Improve KVM's sanity checks for a misconfigured MMU to (hopefully) detect
   all of the ways KVM can botch EFER.LMA vs. CR4.PAE.

 - Remove the "full" out-param from kvm_x86_ops.flush_tlb_gva() as the param
   is only used to avoid what effectively amounts to a single memory write.

 - Fix a mostly-benign bug where KVM can write through a guest's read-only
   mapping due to not checking the error code when expediting emulated MMIO
   page faults.

 - Honor the guest's view of the "EFER.LMSLE must be zero" defeature so that
   userspace can provide migration compatibility between Rome and Milan+.

 - Pend a KVM_REQ_EVENT request when an exception is morphed into a nested
   VM-Exit, otherwise KVM can fail to actually deliver the nested VM-Exit,
   e.g. when injecting a page fault.

 - Add support for PML on SVM.

 - Add support for virtualizing Bus Lock Detect on SVM, and fix a number of
   DR6 bugs and warts along the way.

 - Misc fixes and cleanups.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
KVM x86 misc changes for 7.4

 - Mask off the address space ID when checking for illegal usage of
   kvm_set_internal_memslot() to prevent false negatives on the sanity check.

 - Explicitly zero reserved flags when delivering a SynIC message to avoid
   leaking a byte of stack information to the guest.

 - Rework TDX's handling of the canonical MMU root level to not rely on
   userspace to fill CPUID correctly, as doing so lets userspace trivially
   trigger a KVM_BUG_ON().

 - Reject KVM_SET_NESTED_STATE if userspace "restores" L1 with EFER.LMA=1 &amp;&amp;
   EFER.LME=0, which confuses KVM into trying to configure an 64-bit MMU
   without PAE.

 - Ignore EFER.LMA (clear it from KVM's cached save state) if EFER.LME=0 when
   preparing L2 state, to fix another way to confuse KVM's MMU (and because
   real hardware also ignores EFER.LMA).

 - Improve KVM's sanity checks for a misconfigured MMU to (hopefully) detect
   all of the ways KVM can botch EFER.LMA vs. CR4.PAE.

 - Remove the "full" out-param from kvm_x86_ops.flush_tlb_gva() as the param
   is only used to avoid what effectively amounts to a single memory write.

 - Fix a mostly-benign bug where KVM can write through a guest's read-only
   mapping due to not checking the error code when expediting emulated MMIO
   page faults.

 - Honor the guest's view of the "EFER.LMSLE must be zero" defeature so that
   userspace can provide migration compatibility between Rome and Milan+.

 - Pend a KVM_REQ_EVENT request when an exception is morphed into a nested
   VM-Exit, otherwise KVM can fail to actually deliver the nested VM-Exit,
   e.g. when injecting a page fault.

 - Add support for PML on SVM.

 - Add support for virtualizing Bus Lock Detect on SVM, and fix a number of
   DR6 bugs and warts along the way.

 - Misc fixes and cleanups.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'kvm-x86-coco-7.4' of https://github.com/kvm-x86/linux into HEAD</title>
<updated>2026-10-16T07:45:16+00:00</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2026-10-16T07:45:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=29c925376df478c26415c46561c010d6ca514f8d'/>
<id>29c925376df478c26415c46561c010d6ca514f8d</id>
<content type='text'>
KVM guest_memfd and CoCo changes for 7.4

 - Take the invalidate lock when unbinding a dying file to fix a race with
   kvm_gmem_invalidate_end() that results in KVM leaving the MMU invalidation
   count elevated.  Not taking the lock in the first place was pure misguided
   paranoid.

 - When binding a memslot, purge the bindings if storing the new memslot fails,
   as Xarray's "store range" API can subtly fail partway through.

 - Establish memslot&lt;=&gt;guest_memfd bindings *after* the memslot is ready, as
   the memslot becomes reachable the instant the binding is installed.

 - Don't grab a page refcount when reloading an SNP VMSA and stop returning a
   "struct page" from guest_memfd's PFN lookup altogether, to ensure that KVM
   doesn't hold any unnecessary refcounts (the lifetime of the page is ensured
   by MMU notifiers and similar hooks).  Preventing unnecessary refcounts
   greatly simplifies supporting in-place SHARED=&gt;PRIVATE conversions.

 - Add support for in-place PRIVATE&lt;=&gt;SHARED conversion, i.e. allow a single
   guest_memfd instance to be used for both PRIVATE and SHARED variations of
   CoCo guests' memory (though not at the same time).  This eliminates the need
   to double allocate guest memory for TDX and SNP, and is basically a hard
   requirement for pKVM, which relies on being able to preserve memory contents
   on conversions.

 - Hack-a-fix a deadlock bug in -&gt;error_remove_folio() by returning -EBUSY if
   the filemap invalidate lock is contended.  Punt on a proper fix for the
   moment, as a proper fix likely involves reworking truncate_error_folio().

 - Add a pile of selftests for in-place conversions.

 - Misc guest_memfd cleanups

Conflicts in arch/arm64/kvm/mmu.c: convert to use s2vi.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
KVM guest_memfd and CoCo changes for 7.4

 - Take the invalidate lock when unbinding a dying file to fix a race with
   kvm_gmem_invalidate_end() that results in KVM leaving the MMU invalidation
   count elevated.  Not taking the lock in the first place was pure misguided
   paranoid.

 - When binding a memslot, purge the bindings if storing the new memslot fails,
   as Xarray's "store range" API can subtly fail partway through.

 - Establish memslot&lt;=&gt;guest_memfd bindings *after* the memslot is ready, as
   the memslot becomes reachable the instant the binding is installed.

 - Don't grab a page refcount when reloading an SNP VMSA and stop returning a
   "struct page" from guest_memfd's PFN lookup altogether, to ensure that KVM
   doesn't hold any unnecessary refcounts (the lifetime of the page is ensured
   by MMU notifiers and similar hooks).  Preventing unnecessary refcounts
   greatly simplifies supporting in-place SHARED=&gt;PRIVATE conversions.

 - Add support for in-place PRIVATE&lt;=&gt;SHARED conversion, i.e. allow a single
   guest_memfd instance to be used for both PRIVATE and SHARED variations of
   CoCo guests' memory (though not at the same time).  This eliminates the need
   to double allocate guest memory for TDX and SNP, and is basically a hard
   requirement for pKVM, which relies on being able to preserve memory contents
   on conversions.

 - Hack-a-fix a deadlock bug in -&gt;error_remove_folio() by returning -EBUSY if
   the filemap invalidate lock is contended.  Punt on a proper fix for the
   moment, as a proper fix likely involves reworking truncate_error_folio().

 - Add a pile of selftests for in-place conversions.

 - Misc guest_memfd cleanups

Conflicts in arch/arm64/kvm/mmu.c: convert to use s2vi.
</pre>
</div>
</content>
</entry>
<entry>
<title>Documentation: Add missing KVM s390 crypto attributes</title>
<updated>2026-10-15T11:38:00+00:00</updated>
<author>
<name>Eric Farman</name>
<email>farman@linux.ibm.com</email>
</author>
<published>2026-09-18T14:51:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=bbfbe09b281e2bf80914ea2850dbfb4f953796b0'/>
<id>bbfbe09b281e2bf80914ea2850dbfb4f953796b0</id>
<content type='text'>
Device attributes to enable/disable the AP interpretive execution
support for crypto were added to KVM several years ago, but they
weren't added to the documentation itself.

Fixes: 37940fb0b6a2 ("KVM: s390: device attrs to enable/disable AP interpretation")
Signed-off-by: Eric Farman &lt;farman@linux.ibm.com&gt;
Reviewed-by: Anthony Krowiak &lt;akrowiak@linux.ibm.com&gt;
Signed-off-by: Janosch Frank &lt;frankja@linux.ibm.com&gt;
Signed-off-by: Christian Borntraeger &lt;borntraeger@linux.ibm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Device attributes to enable/disable the AP interpretive execution
support for crypto were added to KVM several years ago, but they
weren't added to the documentation itself.

Fixes: 37940fb0b6a2 ("KVM: s390: device attrs to enable/disable AP interpretation")
Signed-off-by: Eric Farman &lt;farman@linux.ibm.com&gt;
Reviewed-by: Anthony Krowiak &lt;akrowiak@linux.ibm.com&gt;
Signed-off-by: Janosch Frank &lt;frankja@linux.ibm.com&gt;
Signed-off-by: Christian Borntraeger &lt;borntraeger@linux.ibm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch kvm-arm64/pkvm-state-7.4 into kvmarm-master/next</title>
<updated>2026-10-11T09:54:06+00:00</updated>
<author>
<name>Marc Zyngier</name>
<email>maz@kernel.org</email>
</author>
<published>2026-10-11T09:54:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=0ff05136bb0e9b71847eb3a6ea33e512000eb875'/>
<id>0ff05136bb0e9b71847eb3a6ea33e512000eb875</id>
<content type='text'>
* kvm-arm64/pkvm-state-7.4:
  : \
  : State protection for protected pKVM guests, finally starting to deliver
  : on its promises... Patches courtesy of Fuad Tabba.
  :
  : "Following the vCPU state-sync series, this series completes the
  : job for protected VMs: a protected guest's register state stays at
  : EL2, and the host sees only what handling each exit requires."
  : /
  KVM: arm64: Only emulate an SError's entry for vCPUs with NV
  KVM: arm64: Document the protected VM userspace API
  KVM: arm64: Advertise the capabilities that protected VMs support
  KVM: arm64: Reject host power-on of a vCPU that EL2 holds powered off
  KVM: arm64: Reject host access to protected VM private state
  KVM: arm64: Add per-EC entry/exit state marshalling for protected guests
  KVM: arm64: Inject an UNDEF at EL2 for unhandled protected guest exits
  KVM: arm64: Prevent host PC adjustments for protected vCPUs
  KVM: arm64: Restrict KVM_ARM_VCPU_INIT and PSCI version for protected VMs
  KVM: arm64: Handle PSCI calls for protected VMs at EL2
  KVM: arm64: Implement HVC handling for protected guests at EL2
  KVM: arm64: Add system register reset framework for protected VMs
  KVM: arm64: Add {flush,sync}_hyp_timer_state() primitives
  KVM: arm64: Skip fixed-feature state flush for protected vCPUs
  KVM: arm64: Introduce per-EC entry handlers for pKVM
  KVM: arm64: Disable steal time for protected VMs
  KVM: arm64: Pin the host vCPU before adjusting its PC under pKVM
  KVM: arm64: Validate the host vCPU's VM before reading it under pKVM
  KVM: arm64: Sync HCR_EL2.VSE back to the host vCPU under pKVM

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* kvm-arm64/pkvm-state-7.4:
  : \
  : State protection for protected pKVM guests, finally starting to deliver
  : on its promises... Patches courtesy of Fuad Tabba.
  :
  : "Following the vCPU state-sync series, this series completes the
  : job for protected VMs: a protected guest's register state stays at
  : EL2, and the host sees only what handling each exit requires."
  : /
  KVM: arm64: Only emulate an SError's entry for vCPUs with NV
  KVM: arm64: Document the protected VM userspace API
  KVM: arm64: Advertise the capabilities that protected VMs support
  KVM: arm64: Reject host power-on of a vCPU that EL2 holds powered off
  KVM: arm64: Reject host access to protected VM private state
  KVM: arm64: Add per-EC entry/exit state marshalling for protected guests
  KVM: arm64: Inject an UNDEF at EL2 for unhandled protected guest exits
  KVM: arm64: Prevent host PC adjustments for protected vCPUs
  KVM: arm64: Restrict KVM_ARM_VCPU_INIT and PSCI version for protected VMs
  KVM: arm64: Handle PSCI calls for protected VMs at EL2
  KVM: arm64: Implement HVC handling for protected guests at EL2
  KVM: arm64: Add system register reset framework for protected VMs
  KVM: arm64: Add {flush,sync}_hyp_timer_state() primitives
  KVM: arm64: Skip fixed-feature state flush for protected vCPUs
  KVM: arm64: Introduce per-EC entry handlers for pKVM
  KVM: arm64: Disable steal time for protected VMs
  KVM: arm64: Pin the host vCPU before adjusting its PC under pKVM
  KVM: arm64: Validate the host vCPU's VM before reading it under pKVM
  KVM: arm64: Sync HCR_EL2.VSE back to the host vCPU under pKVM

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch kvm-arm64/pre-faulting into kvmarm-master/next</title>
<updated>2026-10-11T09:44:12+00:00</updated>
<author>
<name>Marc Zyngier</name>
<email>maz@kernel.org</email>
</author>
<published>2026-10-11T09:44:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=62449bbaef54cb8170390689569f7fa150abf16a'/>
<id>62449bbaef54cb8170390689569f7fa150abf16a</id>
<content type='text'>
* kvm-arm64/pre-faulting:
  : \
  : Enable stage-2 pre-faulting in the canonical IPA space, implementing the
  : KVM_PRE_FAULT_MEMORY API. Patches courtesy of Lorenzo Stoakes, and based
  : on an initial work by Jack Thomson.
  : /
  KVM: selftests: Add nested pre-fault test for arm64
  KVM: selftests: Add option for different backing in pre-fault tests
  KVM: selftests: Enable pre_fault_memory_test for arm64
  Documentation: KVM: document arm64 KVM_PRE_FAULT_MEMORY
  KVM: arm64: Implement KVM_PRE_FAULT_MEMORY
  KVM: arm64: Pass walk flags to kvm_pgtable_get_leaf()
  KVM: arm64: Propagate EHWPOISON in kvm_s2_fault_pin_pfn()
  KVM: arm64: Size the stage-2 memcache from the fault MMU
  KVM: arm64: Propagate and use kvm_s2_fault_result on S2 fault
  KVM: arm64: Propagate and use mmu in s2fd when handling guest aborts
  KVM: arm64: Propagate and use esr in s2fd when handling guest aborts
  KVM: arm64: Use ESR helpers in guest abort handling
  arm64: Add ESR fault helpers
  KVM: Allow architectures to disallow pre-fault

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* kvm-arm64/pre-faulting:
  : \
  : Enable stage-2 pre-faulting in the canonical IPA space, implementing the
  : KVM_PRE_FAULT_MEMORY API. Patches courtesy of Lorenzo Stoakes, and based
  : on an initial work by Jack Thomson.
  : /
  KVM: selftests: Add nested pre-fault test for arm64
  KVM: selftests: Add option for different backing in pre-fault tests
  KVM: selftests: Enable pre_fault_memory_test for arm64
  Documentation: KVM: document arm64 KVM_PRE_FAULT_MEMORY
  KVM: arm64: Implement KVM_PRE_FAULT_MEMORY
  KVM: arm64: Pass walk flags to kvm_pgtable_get_leaf()
  KVM: arm64: Propagate EHWPOISON in kvm_s2_fault_pin_pfn()
  KVM: arm64: Size the stage-2 memcache from the fault MMU
  KVM: arm64: Propagate and use kvm_s2_fault_result on S2 fault
  KVM: arm64: Propagate and use mmu in s2fd when handling guest aborts
  KVM: arm64: Propagate and use esr in s2fd when handling guest aborts
  KVM: arm64: Use ESR helpers in guest abort handling
  arm64: Add ESR fault helpers
  KVM: Allow architectures to disallow pre-fault

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch kvm-arm64/gicv5-7.4 into kvmarm-master/next</title>
<updated>2026-10-11T09:43:21+00:00</updated>
<author>
<name>Marc Zyngier</name>
<email>maz@kernel.org</email>
</author>
<published>2026-10-11T09:43:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=c439fc93416c02781102589bc60c1e5ef8ba01b6'/>
<id>c439fc93416c02781102589bc60c1e5ef8ba01b6</id>
<content type='text'>
* kvm-arm64/gicv5-7.4: (52 commits)
  : \
  : GICv5 IRS support, courtesy of Sascha Bischoff. From the cover letter:
  :
  : "This series builds on the initial vGICv5 support and adds support
  : for the GICv5 IRS, as described by the GICv5 (EAC0) specification.
  : With this, a GICv5 guest is no longer restricted to PPIs, and can make
  : use of SPIs and LPIs as well."
  : /
  KVM: arm64: vgic-v5: Correctly handle host ISTE __le32 conversion
  KVM: arm64: vgic-v5: Tidy-up programming of vpe descriptor address
  KVM: arm64: vgic-v5: Correctly reset h_lpi_ist to NULL
  KVM: arm64: vgic-v5: Drop __iomem attribute from {vmd,vpet}_base
  KVM: selftests: Add VGICv5 sparse vCPU IDs test
  KVM: selftests: Add VGICv5 IST save/restore coverage
  KVM: selftests: Add VGICv5 LPI delivery tests
  KVM: selftests: Add VGICv5 SPI injection tests
  KVM: selftests: Add VGICv5 CPU sysreg attribute tests
  KVM: selftests: Add VGICv5 USERSPACE_PPIS tests
  KVM: selftests: Add VGICv5 IST attribute tests
  KVM: selftests: Add VGICv5 IRS_REGS attribute tests
  KVM: selftests: Add VGICv5 NR_IRQS attribute tests
  KVM: selftests: Add VGICv5 IRS address attribute tests
  Documentation: KVM: Add the VGICv5 IRS save/restore sequences
  Documentation: KVM: Add docs for KVM_DEV_ARM_VGIC_GRP_IST
  Documentation: KVM: Add KVM_DEV_ARM_VGIC_GRP_IRS_REGS to VGICv5 docs
  Documentation: KVM: Document KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS for VGICv5
  KVM: arm64: gic-v5: Implement save/restore mechanisms for ISTs
  KVM: arm64: gic-v5: Add VGICv5 IST save/restore UAPI
  ...

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* kvm-arm64/gicv5-7.4: (52 commits)
  : \
  : GICv5 IRS support, courtesy of Sascha Bischoff. From the cover letter:
  :
  : "This series builds on the initial vGICv5 support and adds support
  : for the GICv5 IRS, as described by the GICv5 (EAC0) specification.
  : With this, a GICv5 guest is no longer restricted to PPIs, and can make
  : use of SPIs and LPIs as well."
  : /
  KVM: arm64: vgic-v5: Correctly handle host ISTE __le32 conversion
  KVM: arm64: vgic-v5: Tidy-up programming of vpe descriptor address
  KVM: arm64: vgic-v5: Correctly reset h_lpi_ist to NULL
  KVM: arm64: vgic-v5: Drop __iomem attribute from {vmd,vpet}_base
  KVM: selftests: Add VGICv5 sparse vCPU IDs test
  KVM: selftests: Add VGICv5 IST save/restore coverage
  KVM: selftests: Add VGICv5 LPI delivery tests
  KVM: selftests: Add VGICv5 SPI injection tests
  KVM: selftests: Add VGICv5 CPU sysreg attribute tests
  KVM: selftests: Add VGICv5 USERSPACE_PPIS tests
  KVM: selftests: Add VGICv5 IST attribute tests
  KVM: selftests: Add VGICv5 IRS_REGS attribute tests
  KVM: selftests: Add VGICv5 NR_IRQS attribute tests
  KVM: selftests: Add VGICv5 IRS address attribute tests
  Documentation: KVM: Add the VGICv5 IRS save/restore sequences
  Documentation: KVM: Add docs for KVM_DEV_ARM_VGIC_GRP_IST
  Documentation: KVM: Add KVM_DEV_ARM_VGIC_GRP_IRS_REGS to VGICv5 docs
  Documentation: KVM: Document KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS for VGICv5
  KVM: arm64: gic-v5: Implement save/restore mechanisms for ISTs
  KVM: arm64: gic-v5: Add VGICv5 IST save/restore UAPI
  ...

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>KVM: arm64: Fix references to the non-existent VCPU_RUN ioctl</title>
<updated>2026-10-07T10:04:13+00:00</updated>
<author>
<name>Fuad Tabba</name>
<email>fuad.tabba@linux.dev</email>
</author>
<published>2026-09-15T08:44:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=0ab1034969130967bda8e6eab5b8dd6745604f1b'/>
<id>0ab1034969130967bda8e6eab5b8dd6745604f1b</id>
<content type='text'>
There is no VCPU_RUN ioctl. The one that enters the guest is KVM_RUN,
so refer to it by that name.

Signed-off-by: Fuad Tabba &lt;fuad.tabba@linux.dev&gt;
Link: https://patch.msgid.link/20260915084441.3846947-3-fuad.tabba@linux.dev
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There is no VCPU_RUN ioctl. The one that enters the guest is KVM_RUN,
so refer to it by that name.

Signed-off-by: Fuad Tabba &lt;fuad.tabba@linux.dev&gt;
Link: https://patch.msgid.link/20260915084441.3846947-3-fuad.tabba@linux.dev
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>KVM: arm64: Document the protected VM userspace API</title>
<updated>2026-10-02T14:22:40+00:00</updated>
<author>
<name>Fuad Tabba</name>
<email>fuad.tabba@linux.dev</email>
</author>
<published>2026-10-01T13:57:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=61ace86519fb830a7b271c2a1037c8db5f2f3333'/>
<id>61ace86519fb830a7b271c2a1037c8db5f2f3333</id>
<content type='text'>
EL2 owns a protected vCPU's state once it has run, and the ioctls that
would reach it fail rather than operate on the host copy, which holds
the boot state the VMM wrote plus what the exit handlers copy out.
Describe the resulting API in pkvm.rst, point api.rst at it from each
ioctl that behaves differently, and say beside the PVTIME attribute
in devices/vcpu.rst and the PSCI version register in
fw-pseudo-registers.rst how protected VMs differ. The overview also
states the GIC support pKVM enforces: GICv2 is not supported in
protected mode (vgic-v2.c) and GICv5-based guests aren't registered
under pKVM (vgic-v5.c).

Signed-off-by: Fuad Tabba &lt;fuad.tabba@linux.dev&gt;
Link: https://patch.msgid.link/20261001135711.1640520-19-fuad.tabba@linux.dev
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
EL2 owns a protected vCPU's state once it has run, and the ioctls that
would reach it fail rather than operate on the host copy, which holds
the boot state the VMM wrote plus what the exit handlers copy out.
Describe the resulting API in pkvm.rst, point api.rst at it from each
ioctl that behaves differently, and say beside the PVTIME attribute
in devices/vcpu.rst and the PSCI version register in
fw-pseudo-registers.rst how protected VMs differ. The overview also
states the GIC support pKVM enforces: GICv2 is not supported in
protected mode (vgic-v2.c) and GICv5-based guests aren't registered
under pKVM (vgic-v5.c).

Signed-off-by: Fuad Tabba &lt;fuad.tabba@linux.dev&gt;
Link: https://patch.msgid.link/20261001135711.1640520-19-fuad.tabba@linux.dev
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>KVM: x86: Honor the guest's EFER_LMSLE_MBZ</title>
<updated>2026-09-30T21:22:38+00:00</updated>
<author>
<name>Jim Mattson</name>
<email>jmattson@google.com</email>
</author>
<published>2026-09-30T21:21:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=7358d13e1f1975bc8ddd2b02df70d2cdf638273a'/>
<id>7358d13e1f1975bc8ddd2b02df70d2cdf638273a</id>
<content type='text'>
Reject guest attempts to set EFER.LMSLE if userspace enumerates
EFER_LMSLE_MBZ, CPUID.80000008H:EBX[bit 20], in guest CPUID, so that userspace
can hide long mode segment limits from the guest even on CPUs that support
LMSLE, e.g. for migration compatibility between Rome and Milan.

Enumerate the defeature as *partially* emulated, i.e. as supported by KVM but
never advertised, so that kvm_vcpu_after_set_cpuid() propagates userspace's bit
into vcpu-&gt;arch.cpu_caps.  Checking guest_cpu_cap_has() in __kvm_valid_efer()
doesn't suffice on its own, because KVM clears the defeature in kvm_cpu_caps
precisely on the CPUs where it needs to be emulated, i.e. cpu_caps would never
hold the bit no matter what userspace puts in guest CPUID.  Don't advertise the
defeature in KVM_GET_SUPPORTED_CPUID, as that would take EFER.LMSLE away from
userspace that blindly stuffs KVM's supported CPUID into KVM_SET_CPUID2.
MONITOR/MWAIT gets the same treatment.

Enforce the defeature only for guest-initiated writes, as it's a guest CPUID
consistency check, not a host capability.  See commit 11988499e62b ("KVM: x86:
Skip EFER vs. guest CPUID checks for host-initiated writes").  Note,
KVM_SET_SREGS does reject EFER.LMSLE, as it runs the full set of guest CPUID
checks, as does nested VMRUN, i.e. L1 can't sneak EFER.LMSLE into L2 via
vmcb12.

Mask EFER_LMSLE out of the value consumed by efer_trap(), which handles
SVM_EXIT_EFER_WRITE_TRAP.  EFER writes are *trapped*, not intercepted, i.e.
hardware has already committed the write by the time KVM gains control, and
the trap is enabled if and only if the guest is SEV-ES, whose EFER lives in
the encrypted VMSA and so can't be fixed up by KVM.  Rejecting the write would
inject a #GP *and* leave EFER.LMSLE set in the guest, which is strictly worse
than honoring a write that hardware itself allowed.  EFER_SVME is already
masked out for a similar "KVM can't enforce this here" reason.

Opportunistically fix the whitespace damage around __kvm_valid_efer().

Document the resulting two-level contract in api.rst, i.e. that userspace may
set the defeature even when KVM doesn't enumerate it.

Suggested-by: Sean Christopherson &lt;seanjc@google.com&gt;
Assisted-by: LLM
Signed-off-by: Jim Mattson &lt;jmattson@google.com&gt;
Link: https://patch.msgid.link/20260930212114.3500045-3-seanjc@google.com
Signed-off-by: Sean Christopherson &lt;seanjc@google.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Reject guest attempts to set EFER.LMSLE if userspace enumerates
EFER_LMSLE_MBZ, CPUID.80000008H:EBX[bit 20], in guest CPUID, so that userspace
can hide long mode segment limits from the guest even on CPUs that support
LMSLE, e.g. for migration compatibility between Rome and Milan.

Enumerate the defeature as *partially* emulated, i.e. as supported by KVM but
never advertised, so that kvm_vcpu_after_set_cpuid() propagates userspace's bit
into vcpu-&gt;arch.cpu_caps.  Checking guest_cpu_cap_has() in __kvm_valid_efer()
doesn't suffice on its own, because KVM clears the defeature in kvm_cpu_caps
precisely on the CPUs where it needs to be emulated, i.e. cpu_caps would never
hold the bit no matter what userspace puts in guest CPUID.  Don't advertise the
defeature in KVM_GET_SUPPORTED_CPUID, as that would take EFER.LMSLE away from
userspace that blindly stuffs KVM's supported CPUID into KVM_SET_CPUID2.
MONITOR/MWAIT gets the same treatment.

Enforce the defeature only for guest-initiated writes, as it's a guest CPUID
consistency check, not a host capability.  See commit 11988499e62b ("KVM: x86:
Skip EFER vs. guest CPUID checks for host-initiated writes").  Note,
KVM_SET_SREGS does reject EFER.LMSLE, as it runs the full set of guest CPUID
checks, as does nested VMRUN, i.e. L1 can't sneak EFER.LMSLE into L2 via
vmcb12.

Mask EFER_LMSLE out of the value consumed by efer_trap(), which handles
SVM_EXIT_EFER_WRITE_TRAP.  EFER writes are *trapped*, not intercepted, i.e.
hardware has already committed the write by the time KVM gains control, and
the trap is enabled if and only if the guest is SEV-ES, whose EFER lives in
the encrypted VMSA and so can't be fixed up by KVM.  Rejecting the write would
inject a #GP *and* leave EFER.LMSLE set in the guest, which is strictly worse
than honoring a write that hardware itself allowed.  EFER_SVME is already
masked out for a similar "KVM can't enforce this here" reason.

Opportunistically fix the whitespace damage around __kvm_valid_efer().

Document the resulting two-level contract in api.rst, i.e. that userspace may
set the defeature even when KVM doesn't enumerate it.

Suggested-by: Sean Christopherson &lt;seanjc@google.com&gt;
Assisted-by: LLM
Signed-off-by: Jim Mattson &lt;jmattson@google.com&gt;
Link: https://patch.msgid.link/20260930212114.3500045-3-seanjc@google.com
Signed-off-by: Sean Christopherson &lt;seanjc@google.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
