Changes in Makefile

0fc8f6200d2313278fbf4539bbab74677c685531 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 27 Apr 2026 10:26:49 +0200

Merge drm/drm-fixes into drm-misc-fixesGetting fixes and updates from v7.1-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

01f492e1817e858d1712f2489d0afbaa552f417b - Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm

Fri, 17 Apr 2026 16:18:03 +0200

Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvmPull kvm updates from Paolo Bonzini: "Arm: - Add support for tracing in the standalone EL2 hypervisor code, which should help both debugging and performance analysis. This uses the new infrastructure for 'remote' trace buffers that can be exposed by non-kernel entities such as firmware, and which came through the tracing tree - Add support for GICv5 Per Processor Interrupts (PPIs), as the starting point for supporting the new GIC architecture in KVM - Finally add support for pKVM protected guests, where pages are unmapped from the host as they are faulted into the guest and can be shared back from the guest using pKVM hypercalls. Protected guests are created using a new machine type identifier. As the elusive guestmem has not yet delivered on its promises, anonymous memory is also supported This is only a first step towards full isolation from the host; for example, the CPU register state and DMA accesses are not yet isolated. Because this does not really yet bring fully what it promises, it is hidden behind CONFIG_ARM_PKVM_GUEST + 'kvm-arm.mode=protected', and also triggers TAINT_USER when a VM is created. Caveat emptor - Rework the dreaded user_mem_abort() function to make it more maintainable, reducing the amount of state being exposed to the various helpers and rendering a substantial amount of state immutable - Expand the Stage-2 page table dumper to support NV shadow page tables on a per-VM basis - Tidy up the pKVM PSCI proxy code to be slightly less hard to follow - Fix both SPE and TRBE in non-VHE configurations so that they do not generate spurious, out of context table walks that ultimately lead to very bad HW lockups - A small set of patches fixing the Stage-2 MMU freeing in error cases - Tighten-up accepted SMC immediate value to be only #0 for host SMCCC calls - The usual cleanups and other selftest churn LoongArch: - Use CSR_CRMD_PLV for kvm_arch_vcpu_in_kernel() - Add DMSINTC irqchip in kernel support RISC-V: - Fix steal time shared memory alignment checks - Fix vector context allocation leak - Fix array out-of-bounds in pmu_ctr_read() and pmu_fw_ctr_read_hi() - Fix double-free of sdata in kvm_pmu_clear_snapshot_area() - Fix integer overflow in kvm_pmu_validate_counter_mask() - Fix shift-out-of-bounds in make_xfence_request() - Fix lost write protection on huge pages during dirty logging - Split huge pages during fault handling for dirty logging - Skip CSR restore if VCPU is reloaded on the same core - Implement kvm_arch_has_default_irqchip() for KVM selftests - Factored-out ISA checks into separate sources - Added hideleg to struct kvm_vcpu_config - Factored-out VCPU config into separate sources - Support configuration of per-VM HGATP mode from KVM user space s390: - Support for ESA (31-bit) guests inside nested hypervisors - Remove restriction on memslot alignment, which is not needed anymore with the new gmap code - Fix LPSW/E to update the bear (which of course is the breaking event address register) x86: - Shut up various UBSAN warnings on reading module parameter before they were initialized - Don't zero-allocate page tables that are used for splitting hugepages in the TDP MMU, as KVM is guaranteed to set all SPTEs in the page table and thus write all bytes - As an optimization, bail early when trying to unsync 4KiB mappings if the target gfn can just be mapped with a 2MiB hugepage x86 generic: - Copy single-chunk MMIO write values into struct kvm_vcpu (more precisely struct kvm_mmio_fragment) to fix use-after-free stack bugs where KVM would dereference stack pointer after an exit to userspace - Clean up and comment the emulated MMIO code to try to make it easier to maintain (not necessarily "easy", but "easier") - Move VMXON+VMXOFF and EFER.SVME toggling out of KVM (not *all* of VMX and SVM enabling) as it is needed for trusted I/O - Advertise support for AVX512 Bit Matrix Multiply (BMM) instructions - Immediately fail the build if a required #define is missing in one of KVM's headers that is included multiple times - Reject SET_GUEST_DEBUG with -EBUSY if there's an already injected exception, mostly to prevent syzkaller from abusing the uAPI to trigger WARNs, but also because it can help prevent userspace from unintentionally crashing the VM - Exempt SMM from CPUID faulting on Intel, as per the spec - Misc hardening and cleanup changes x86 (AMD): - Fix and optimize IRQ window inhibit handling for AVIC; make it per-vCPU so that KVM doesn't prematurely re-enable AVIC if multiple vCPUs have to-be-injected IRQs - Clean up and optimize the OSVW handling, avoiding a bug in which KVM would overwrite state when enabling virtualization on multiple CPUs in parallel. This should not be a problem because OSVW should usually be the same for all CPUs - Drop a WARN in KVM_MEMORY_ENCRYPT_REG_REGION where KVM complains about a "too large" size based purely on user input - Clean up and harden the pinning code for KVM_MEMORY_ENCRYPT_REG_REGION - Disallow synchronizing a VMSA of an already-launched/encrypted vCPU, as doing so for an SNP guest will crash the host due to an RMP violation page fault - Overhaul KVM's APIs for detecting SEV+ guests so that VM-scoped queries are required to hold kvm->lock, and enforce it by lockdep. Fix various bugs where sev_guest() was not ensured to be stable for the whole duration of a function or ioctl - Convert a pile of kvm->lock SEV code to guard() - Play nicer with userspace that does not enable KVM_CAP_EXCEPTION_PAYLOAD, for which KVM needs to set CR2 and DR6 as a response to ioctls such as KVM_GET_VCPU_EVENTS (even if the payload would end up in EXITINFO2 rather than CR2, for example). Only set CR2 and DR6 when consumption of the payload is imminent, but on the other hand force delivery of the payload in all paths where userspace retrieves CR2 or DR6 - Use vcpu->arch.cr2 when updating vmcb12's CR2 on nested #VMEXIT instead of vmcb02->save.cr2. The value is out of sync after a save/restore or after a #PF is injected into L2 - Fix a class of nSVM bugs where some fields written by the CPU are not synchronized from vmcb02 to cached vmcb12 after VMRUN, and so are not up-to-date when saved by KVM_GET_NESTED_STATE - Fix a class of bugs where the ordering between KVM_SET_NESTED_STATE and KVM_SET_{S}REGS could cause vmcb02 to be incorrectly initialized after save+restore - Add a variety of missing nSVM consistency checks - Fix several bugs where KVM failed to correctly update VMCB fields on nested #VMEXIT - Fix several bugs where KVM failed to correctly synthesize #UD or #GP for SVM-related instructions - Add support for save+restore of virtualized LBRs (on SVM) - Refactor various helpers and macros to improve clarity and (hopefully) make the code easier to maintain - Aggressively sanitize fields when copying from vmcb12, to guard against unintentionally allowing L1 to utilize yet-to-be-defined features - Fix several bugs where KVM botched rAX legality checks when emulating SVM instructions. There are remaining issues in that KVM doesn't handle size prefix overrides for 64-bit guests - Fail emulation of VMRUN/VMLOAD/VMSAVE if mapping vmcb12 fails instead of somewhat arbitrarily synthesizing #GP (i.e. don't double down on AMD's architectural but sketchy behavior of generating #GP for "unsupported" addresses) - Cache all used vmcb12 fields to further harden against TOCTOU bugs x86 (Intel): - Drop obsolete branch hint prefixes from the VMX instruction macros - Use ASM_INPUT_RM() in __vmcs_writel() to coerce clang into using a register input when appropriate - Code cleanups guest_memfd: - Don't mark guest_memfd folios as accessed, as guest_memfd doesn't support reclaim, the memory is unevictable, and there is no storage to write back to LoongArch selftests: - Add KVM PMU test cases s390 selftests: - Enable more memory selftests x86 selftests: - Add support for Hygon CPUs in KVM selftests - Fix a bug in the MSR test where it would get false failures on AMD/Hygon CPUs with exactly one of RDPID or RDTSCP - Add an MADV_COLLAPSE testcase for guest_memfd as a regression test for a bug where the kernel would attempt to collapse guest_memfd folios against KVM's will"* tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (373 commits) KVM: x86: use inlines instead of macros for is_sev_*guest x86/virt: Treat SVM as unsupported when running as an SEV+ guest KVM: SEV: Goto an existing error label if charging misc_cg for an ASID fails KVM: SVM: Move lock-protected allocation of SEV ASID into a separate helper KVM: SEV: use mutex guard in snp_handle_guest_req() KVM: SEV: use mutex guard in sev_mem_enc_unregister_region() KVM: SEV: use mutex guard in sev_mem_enc_ioctl() KVM: SEV: use mutex guard in snp_launch_update() KVM: SEV: Assert that kvm->lock is held when querying SEV+ support KVM: SEV: Document that checking for SEV+ guests when reclaiming memory is "safe" KVM: SEV: Hide "struct kvm_sev_info" behind CONFIG_KVM_AMD_SEV=y KVM: SEV: WARN on unhandled VM type when initializing VM KVM: LoongArch: selftests: Add PMU overflow interrupt test KVM: LoongArch: selftests: Add basic PMU event counting test KVM: LoongArch: selftests: Add cpucfg read/write helpers LoongArch: KVM: Add DMSINTC inject msi to vCPU LoongArch: KVM: Add DMSINTC device support LoongArch: KVM: Make vcpu_is_preempted() as a macro rather than function LoongArch: KVM: Move host CSR_GSTAT save and restore in context switch LoongArch: KVM: Move host CSR_EENTRY save and restore in context switch ... List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

e74c3a8891c05f88eeb87121de7e12dc95766a4a - Merge tag 'kvmarm-7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD

Mon, 13 Apr 2026 11:49:54 +0200

Merge tag 'kvmarm-7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEADKVM/arm64 updates for 7.1* New features:- Add support for tracing in the standalone EL2 hypervisor code, which should help both debugging and performance analysis. This comes with a full infrastructure for 'remote' trace buffers that can be exposed by non-kernel entities such as firmware.- Add support for GICv5 Per Processor Interrupts (PPIs), as the starting point for supporting the new GIC architecture in KVM.- Finally add support for pKVM protected guests, with anonymous memory being used as a backing store. About time!* Improvements and bug fixes:- Rework the dreaded user_mem_abort() function to make it more maintainable, reducing the amount of state being exposed to the various helpers and rendering a substantial amount of state immutable.- Expand the Stage-2 page table dumper to support NV shadow page tables on a per-VM basis.- Tidy up the pKVM PSCI proxy code to be slightly less hard to follow.- Fix both SPE and TRBE in non-VHE configurations so that they do not generate spurious, out of context table walks that ultimately lead to very bad HW lockups.- A small set of patches fixing the Stage-2 MMU freeing in error cases.- Tighten-up accepted SMC immediate value to be only #0 for host SMCCC calls.- The usual cleanups and other selftest churn. List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

f8078d51ee232c8d4fa552d30e06c641b944e2c2 - Merge branch kvm-arm64/vgic-v5-ppi into kvmarm-master/next

Wed, 08 Apr 2026 13:22:35 +0200

Merge branch kvm-arm64/vgic-v5-ppi into kvmarm-master/next* kvm-arm64/vgic-v5-ppi: (40 commits) : . : Add initial GICv5 support for KVM guests, only adding PPI support : for the time being. Patches courtesy of Sascha Bischoff. : : From the cover letter: : : "This is v7 of the patch series to add the virtual GICv5 [1] device : (vgic_v5). Only PPIs are supported by this initial series, and the : vgic_v5 implementation is restricted to the CPU interface, : only. Further patch series are to follow in due course, and will add : support for SPIs, LPIs, the GICv5 IRS, and the GICv5 ITS." : . KVM: arm64: selftests: Add no-vgic-v5 selftest KVM: arm64: selftests: Introduce a minimal GICv5 PPI selftest KVM: arm64: gic-v5: Communicate userspace-driveable PPIs via a UAPI Documentation: KVM: Introduce documentation for VGICv5 KVM: arm64: gic-v5: Probe for GICv5 device KVM: arm64: gic-v5: Set ICH_VCTLR_EL2.En on boot KVM: arm64: gic-v5: Introduce kvm_arm_vgic_v5_ops and register them KVM: arm64: gic-v5: Hide FEAT_GCIE from NV GICv5 guests KVM: arm64: gic: Hide GICv5 for protected guests KVM: arm64: gic-v5: Mandate architected PPI for PMU emulation on GICv5 KVM: arm64: gic-v5: Enlighten arch timer for GICv5 irqchip/gic-v5: Introduce minimal irq_set_type() for PPIs KVM: arm64: gic-v5: Initialise ID and priority bits when resetting vcpu KVM: arm64: gic-v5: Create and initialise vgic_v5 KVM: arm64: gic-v5: Support GICv5 interrupts with KVM_IRQ_LINE KVM: arm64: gic-v5: Implement direct injection of PPIs KVM: arm64: Introduce set_direct_injection irq_op KVM: arm64: gic-v5: Trap and mask guest ICC_PPI_ENABLERx_EL1 writes KVM: arm64: gic-v5: Check for pending PPIs KVM: arm64: gic-v5: Clear TWI if single task running ...Signed-off-by: Marc Zyngier List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

af325e87af5da2f686d1ad547edc96f731418f2a - KVM: arm64: gic-v5: Add vgic-v5 save/restore hyp interface

Thu, 19 Mar 2026 16:53:52 +0100

KVM: arm64: gic-v5: Add vgic-v5 save/restore hyp interfaceIntroduce the following hyp functions to save/restore GICv5 state:* __vgic_v5_save_apr()* __vgic_v5_restore_vmcr_apr()* __vgic_v5_save_ppi_state() - no hypercall required* __vgic_v5_restore_ppi_state() - no hypercall required* __vgic_v5_save_state() - no hypercall required* __vgic_v5_restore_state() - no hypercall requiredNote that the functions tagged as not requiring hypercalls are alwayscalled directly from the same context. They are either called via thevgic_save_state()/vgic_restore_state() path when running with VHE, orvia __hyp_vgic_save_state()/__hyp_vgic_restore_state() otherwise. Thismimics how vgic_v3_save_state()/vgic_v3_restore_state() areimplemented.Overall, the state of the following registers is saved/restored:* ICC_ICSR_EL1* ICH_APR_EL2* ICH_PPI_ACTIVERx_EL2* ICH_PPI_DVIRx_EL2* ICH_PPI_ENABLERx_EL2* ICH_PPI_PENDRx_EL2* ICH_PPI_PRIORITYRx_EL2* ICH_VMCR_EL2All of these are saved/restored to/from the KVM vgic_v5 CPUIF shadowstate, with the exception of the PPI active, pending, and enablestate. The pending state is saved and restored from kvm_host_data asany changes here need to be tracked and propagated back to thevgic_irq shadow structures (coming in a future commit). Therefore, anentry and an exit copy is required. The active and enable state isrestored from the vgic_v5 CPUIF, but is saved to kvm_host_data. Again,this needs to by synced back into the shadow data structures.The ICSR must be save/restored as this register is shared between hostand guest. Therefore, to avoid leaking host state to the guest, thismust be saved and restored. Moreover, as this can by used by the hostat any time, it must be save/restored eagerly. Note: the host state isnot preserved as the host should only use this register whenpreemption is disabled.As with GICv3, the VMCR is eagerly saved as this is required whenchecking if interrupts can be injected or not, and therefore impactsthings such as WFI.As part of restoring the ICH_VMCR_EL2 and ICH_APR_EL2, GICv3-compatmode is also disabled by setting the ICH_VCTLR_EL2.V3 bit to 0. Thecorrespoinding GICv3-compat mode enable is part of the VMCR & APRrestore for a GICv3 guest as it only takes effect when actuallyrunning a guest.Co-authored-by: Timothy Hayes Signed-off-by: Timothy Hayes Signed-off-by: Sascha Bischoff Link: https://patch.msgid.link/20260319154937.3619520-17-sascha.bischoff@arm.comSigned-off-by: Marc Zyngier List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

c771600c6af14749609b49565ffb4cac2959710d - Merge drm/drm-next into drm-intel-gt-next

Wed, 05 Feb 2025 10:29:14 +0100

Merge drm/drm-next into drm-intel-gt-nextWe need4ba4f1afb6a9 ("perf: Generic hotplug support for a PMU with a scope")in order to land a i915 PMU simplification and a fix. That landed in 6.12and we are stuck at 6.9 so lets bump things forward.Signed-off-by: Tvrtko Ursulin List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

3fd6c59042dbba50391e30862beac979491145fe - Merge tag 'v6.12-rc1' into clk-meson-next

Mon, 30 Sep 2024 11:28:07 +0200

Merge tag 'v6.12-rc1' into clk-meson-nextLinux 6.12-rc1 List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

c7c3c7b7400bef1ba14831c0a8ca1cdb35f32c94 - Merge drm/drm-next into drm-xe-next

Wed, 11 Sep 2024 22:23:00 +0200

Merge drm/drm-next into drm-xe-nextSync with drm-misc and drm-intel-next for common APIs and refactors.Signed-off-by: Lucas De Marchi List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

3973a8d052829dcc5193fb6330dcd13c2b7127ca - Merge drm/drm-next into drm-misc-next

Fri, 30 Aug 2024 14:14:29 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get fixes from v6.11-rc5.Signed-off-by: Thomas Zimmermann List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

2cd86f02c017bf9733e5cd891381b7d40f6f37ad - Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes

Tue, 01 Oct 2024 18:09:41 +0200

Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixesRequired for a panthor fix that broke whenFOP_UNSIGNED_OFFSET was added in place of FMODE_UNSIGNED_OFFSET.Signed-off-by: Maarten Lankhorst List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

87ee9981d1f86ee9b1623a46c7f9e4ac24461fe4 - Merge 6.11-rc4 into driver-core-next

Mon, 19 Aug 2024 06:07:49 +0200

Merge 6.11-rc4 into driver-core-nextWe need the driver core build fixes in here as well.Signed-off-by: Greg Kroah-Hartman List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

ebbe30f4bba127505c5664dd67f519e5e06d16be - Merge 6.11-rc4 into tty-next

Mon, 19 Aug 2024 06:24:50 +0200

Merge 6.11-rc4 into tty-nextWe need the tty/serial fixes in here as well.Signed-off-by: Greg Kroah-Hartman List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

ca7df2c7bb5f83fe46aa9ce998b7352c6b28f3a1 - Merge 6.11-rc4 into usb-next

Mon, 19 Aug 2024 06:16:49 +0200

Merge 6.11-rc4 into usb-nextWe need the usb / thunderbolt fixes in here as well.Signed-off-by: Greg Kroah-Hartman List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

10c8d1bd786508e996837d5d4b125c69315c5529 - Merge 6.11-rc4 into char-misc-next

Mon, 19 Aug 2024 06:02:26 +0200

Merge 6.11-rc4 into char-misc-nextWe need the char/misc fixes in here as well.Signed-off-by: Greg Kroah-Hartman List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

42b16d3ac371a2fac9b6f08fd75f23f34ba3955a - Merge tag 'v6.11' into for-6.12/block

Tue, 17 Sep 2024 16:32:53 +0200

Merge tag 'v6.11' into for-6.12/blockMerge in 6.11 final to get the fix for preventing deadlocks on anelevator switch, as there's a fixup for that patch.* tag 'v6.11': (1788 commits) Linux 6.11 Revert "KVM: VMX: Always honor guest PAT on CPUs that support self-snoop" pinctrl: pinctrl-cy8c95x0: Fix regcache cifs: Fix signature miscalculation mm: avoid leaving partial pfn mappings around in error case drm/xe/client: add missing bo locking in show_meminfo() drm/xe/client: fix deadlock in show_meminfo() drm/xe/oa: Enable Xe2+ PES disaggregation drm/xe/display: fix compat IS_DISPLAY_STEP() range end drm/xe: Fix access_ok check in user_fence_create drm/xe: Fix possible UAF in guc_exec_queue_process_msg drm/xe: Remove fence check from send_tlb_invalidation drm/xe/gt: Remove double include net: netfilter: move nf flowtable bpf initialization in nf_flow_table_module_init() PCI: Fix potential deadlock in pcim_intx() workqueue: Clear worker->pool in the worker thread context net: tighten bad gso csum offset check in virtio_net_hdr netlink: specs: mptcp: fix port endianness net: dpaa: Pad packets to ETH_ZLEN mptcp: pm: Fix uaf in __timer_delete_sync ... List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

36ec807b627b4c0a0a382f0ae48eac7187d14b2b - Merge branch 'next' into for-linus

Fri, 20 Sep 2024 10:24:24 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.12 merge window. List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

f057b57270c2a17d3f45c177e9434fa5745caa48 - Merge branch 'ib/6.11-rc6-matrix-keypad-spitz' into next

Fri, 06 Sep 2024 06:49:07 +0200

Merge branch 'ib/6.11-rc6-matrix-keypad-spitz' into nextBring in changes removing support for platform data from matrix-keypaddriver. List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

34cd19288161313b6ba24004206ab6a64fdef7c5 - Merge branch 'bnxt_re_variable_wqes' into rdma.git for-next

Tue, 27 Aug 2024 15:32:25 +0200

Merge branch 'bnxt_re_variable_wqes' into rdma.git for-nextSelvin Xavier says:=============Enable the Variable size Work Queue entry support for Gen P7adapters. This would help in the better utilization of the queue memoryand pci bandwidth due to the smaller send queue Work entries.=============Based on v6.11-rc5 for dependencies.* bnxt_re_variable_wqes: (829 commits) RDMA/bnxt_re: Enable variable size WQEs for user space applications RDMA/bnxt_re: Handle variable WQE support for user applications RDMA/bnxt_re: Fix the table size for PSN/MSN entries RDMA/bnxt_re: Get the WQE index from slot index while completing the WQEs RDMA/bnxt_re: Add support for Variable WQE in Genp7 adapters Linux 6.11-rc5 ...Signed-off-by: Jason Gunthorpe List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

76889bbaabf5cab981a74ed69cb3816921edc5d4 - Merge branch 'nesting_reserved_regions' into iommufd.git for-next

Tue, 27 Aug 2024 16:13:56 +0200

Merge branch 'nesting_reserved_regions' into iommufd.git for-nextNicolin Chen says:=========IOMMU_RESV_SW_MSI is a unique region defined by an IOMMU driver. Though itis eventually used by a device for address translation to an MSI location(including nested cases), practically it is a universal region across alldomains allocated for the IOMMU that defines it.Currently IOMMUFD core fetches and reserves the region during an attach toan hwpt_paging. It works with a hwpt_paging-only case, but might not workwith a nested case where a device could directly attach to a hwpt_nested,bypassing the hwpt_paging attachment.Move the enforcement forward, to the hwpt_paging allocation function. Thenclean up all the SW_MSI related things in the attach/replace routine.=========Based on v6.11-rc5 for dependencies.* nesting_reserved_regions: (562 commits) iommufd/device: Enforce reserved IOVA also when attached to hwpt_nested Linux 6.11-rc5 ... List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile

c24999e61b2187578fe4256b7bc6190a046c4b93 - Merge tag 'i2c-host-6.12' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-mergewindow

Sat, 21 Sep 2024 12:46:00 +0200

Merge tag 'i2c-host-6.12' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-mergewindowThe DesignWare and the Renesas I2C drivers have received most ofthe changes in this pull request.The first has has undergone through a series of cleanups thathave been sent to the mailing list a year ago for the first timeand finally get merged in this pull request. They are many, fromtypos (e.g. i2/i2c), to cosmetics, to refactoring (e.g. moveinline functions to librarieas) and many others.Besides that, all the DesignWare Kconfig options have beengrouped under the I2C_DESIGNWARE_CORE and this required someadaptation in many of the kernel configuration files fordifferent arm and mips boards.Follows the list of the rest of the changes grouped by type ofchange.Cleanups--------The Qualcomm Geni platform improves the exit path in the runtimeresume function.The Intel LJCA driver loses "target_addr" parameter inljca_i2c_stop() because it was unused.The MediaTek controller intializes the restart_flag in thetransfer function using the ternary conditional operator ("? :")instead of initializing it in different parts.Constified a few global data structures in the virtio driver.The Renesas driver simplifies the bus speed handling in the initfunction making it more readable.Improved an if/else statement in probe function of the RenesasR-Car driver.The iMX/MXC driver switches to using the RUNTIME_PM_OPS() insteadof SET_RUNTIME_PM_OPS().Still in the iMX/MXC driver a comma ',' has been replaced by asemicolon ';', while in different drivers the ',' has beenremoved from the '{ }' delimiters.Finally three devm_clk_get_enabled() have been used to simplifythe devm_clk_get/clk_prepare_enable tuple in the Renesas EMEV2,Ingenic and MPC drivers.Refactors---------The Nuvoton fixes a potential out of boundary array access. Thisis not a bug fix because the issue could never occur due tohardware not having the properties listed in the array. Thechange makes the driver more future proof and, at the same time,silences code analyzers.Improvements------------The Renesas I2C (riic) driver undergoes several patches improvingthe runtime power management handling.The Intel i801 driver uses a more descriptive adapter's name toshow the presence of the IDF feature.In the Intel Denverton (ismt) adapter the pending transactionsare killed when irq's can't complete their handling, triggering atimeout. This could have been considered as a bug fix, butbecause, standing to Vasily, it's very sporadic, I preferredconsidering the patch rather as an improvement.New Feature-----------The Renesas I2C (riic) driver now supports the fast mode plus.New support-----------Added support for: - Renesas R9A08G045 - Rockchip RK3576 - KEBA I2C - Theobroma Systems Mule Multiplexer.The Keba comes with a new driver, i2c-keba.c.The Mule is an i2c multiplexer and it also comes with a newdriver, mux/i2c-mux-mule.c.Core patch----------This pull request includes also a patch in the I2C framework, ini2c-core-base.c where the runtime PM functions have been replacedin order to allow to be accessed during the device add.Devicetree----------Some cleanups in the devicetree, as well. nVidia and Qualcommbindings improve their "if:then:" blocks. While the aspeedbinding loses the "multi-master" property because it wasredundant.The i2c-sprd binding has been converted to YAML. List of files: /linux/arch/arm64/kvm/hyp/vhe/Makefile