<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sysreg</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1017911fcc03584b6854b1b8f0aafeb25f5a8d25 - irqchip/gic-v5: Preserve ICC_CR0_EL1 state</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#1017911fcc03584b6854b1b8f0aafeb25f5a8d25</link>
        <description>irqchip/gic-v5: Preserve ICC_CR0_EL1 stateIn addition to EN, ICC_CR0_EL1 contains other fields, such as LINK andLINK_IDLE. The driver only needs to modify EN, and must preserve thevalues of all other fields when enabling or disabling the CPUinterface.Define the missing LINK and LINK_IDLE fields, and use read-modify-writeaccesses to update EN without affecting the rest of ICC_CR0_EL1.Fixes: 7ec80fb3f025 (&quot;irqchip/gic-v5: Add GICv5 PPI support&quot;)Reported-by: Sashiko &lt;sashiko-bot@kernel.org&gt;Signed-off-by: Sascha Bischoff &lt;sascha.bischoff@arm.com&gt;Signed-off-by: Thomas Gleixner &lt;tglx@kernel.org&gt;Reviewed-by: Marc Zyngier &lt;maz@kernel.org&gt;Link: https://patch.msgid.link/20260907164945.714545-1-sascha.bischoff@arm.comCloses: https://lore.kernel.org/r/20260807121703.D4B7A1F00A3A@smtp.kernel.org

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 07 Sep 2026 18:49:50 +0200</pubDate>
        <dc:creator>Sascha Bischoff &lt;Sascha.Bischoff@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>7bb6284aa7b3c369b41e7f33fcbe193161f008e7 - Merge tag &apos;for-linus&apos; of git://git.kernel.org/pub/scm/virt/kvm/kvm</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#7bb6284aa7b3c369b41e7f33fcbe193161f008e7</link>
        <description>Merge tag &apos;for-linus&apos; of git://git.kernel.org/pub/scm/virt/kvm/kvmPull kvm updates from Paolo Bonzini: &quot;ARM64:   - Add support for &apos;slot&apos; based PMU events, paired with new UAPI that     compels the user to select a specific PMU implementation   - Lazy save/restore of vCPU state for pKVM, along with various fixes     and cleanups to the management of vCPU state between the untrusted     host and pKVM hypervisor   - Disable traps of EL1 registers for nested hypervisors when     FEAT_NV2p1 is present, guaranteeing that EL2-specific register bits     are stateful in the EL1 counterpart   - Leverage FEAT_NV3 to avoid unnecessary ERET/TLBI traps when the     scope of those instructions remains &apos;in host&apos; (i.e. L1     kernel/userspace)   - Pile of fixes for the management of the VNCR pseudo-TLB, such as     under-invalidations and races with concurrent TLBIs on other vCPUs   - Consolidate the non-protected and pKVM view of ICH_VTR_EL2 to a     runtime-patched constant, allowing the same data to be shared with     pKVM prior to dropping host privileges   - Considerable pile of LLM-assisted fixes around the shop but mostly     in the VGIC, our in-kernel generator of bugs (and sometimes     interrupts)  LoongArch:   - Advertise already-supported capabilities   - Some bug fixes about timer and MMIO   - Some hardening about interrupt injection   - Replace kvm_err() with kvm_pr_unimpl()   - Add FPU/LSX/LASX test cases for selftests  RISC-V:   - Svadu/Zicfiss/Zicfilp FWFT support for Guest   - Use try_cmpxchg for IMSIC MRIF RMW   - More arch-specific tracepoints in KVM RISC-V   - Eager page splitting when enabling dirty logging   - Optimize hfence request handling for SMP Guests   - Improve dirty log clearing by skipping zero bits in mask   - Guard HFENCE range loops against overflow   - CPU PM notifiers in KVM RISC-V for non-retentive idle states   - Fix kernel-mode vector context save/restore for Guest  s390:   - Fixes for vfio-ap   - Fixes for the gmap rework   - Fixes for vsie   - AI triggered fixes all over   - diag9c tracing   - code move preparation for the additional arm64 support   - enable CONTEXT_ANALYSIS  x86:   - Perform spring cleaning on x86.{c,h} and asm/kvm_host.h, by adding     regs.c (the kvm_cache_regs.h =&gt; regs.h is already applied) and     msrs.{c,h}, and moving relevant code out of x86.c   - Split kvm_mmu in three parts, respectively to describe the format     of page tables, walking the guest page tables and building the page     tables. Always use the same page table walker kvm-&gt;arch.gva_walk as     the entry point to convert a guest&apos;s virtual address, where the     previous code used two different kvm_mmu structs depending on     whether the walk included nested EPT/NPT or not. Make page fault     vmexits reuse the permission checking machinery that is used for     guest page faults. This is both a cleanup and a baby step towards     supporting XS/XU memory permissions   - Document some of the &quot;fun&quot; gotchas with the APIC base when creating     IRQCHIPs on x86   - Remove a defunct masterclock update from kvm_xen_shared_info_init().     It could result in incorrect kvmclock due to triggering an     unnecessary switch to/from masterclock mode   - Skip Xen runstate time updates if time has effectively gone     backwards, so that the guest doesn&apos;t report 100% steal time for     a very, very long time   - Drop KVM&apos;s runtime updates of the Xen PV timing CPUID leaf, as KVM     was updating the wrong sub-leaf, and upstream KVM will soon provide     all the information needed by userspace to populate the CPUID field     itself   - Fix a bug where KVM would walk a newly created rmap without holding     the rmap lock (or mmu_lock) during aging   - Fix a bug where aging TDP MMU SPTEs could clobber FROZEN SPTEs   - Fix a variety of #DB priority bugs   - Fix a class of races related to enabling Hyper-V emulation on a     vCPU after the vCPU is visible to the rest of KVM   - Use static calls for nested virtualization ops   - Move more KVM-internal code out of x86&apos;s kvm_host.h   - Enumerate support for a variety of Zhaoxin instructions that don&apos;t     require explicit virtualization   - Fix missing EFER validation bugs, including in the KVM_SET_SREGS*     path   - Harden kvm_vcpu_map() against double-mapping and thus leaking     references   - Misc fixes and cleanups, e.g. for largely benign syzkaller splats  x86 (Intel):   - Zero a vCPU&apos;s entry in VMX&apos;s Posted Interrupt Descriptor table used     for IPI virtualization when the vCPU is freed, to fix a     use-after-free where hardware will write to a freed vCPU&apos;s PID   - Service local TLB flushes on a failed nested VM-Enter to fix a bug     where KVM could miss a TLB on a future, successful VM-Enter with     the same L2 VPID   - Cap the maximum value shoved into the VMX Preemption Timer to     workaround an erratum that affects all existing Intel CPUs that     support CPUID 0x15   - Fix VPID virtualization bugs where KVM would fail to flush hardware     TLBs   - Harden the TDX &quot;populate&quot; ioctls against bad input, and to prepare     for supporting in-place private&lt;=&gt;shared conversion  x86 (AMD):   - Forcefully invalidate SNP VMSA pages if their backing guest_memfd     page is zapped/invalidated, e.g. due to a PUNCH_HOLE in response to     a Page-State Change request   - Remove a dying VM from the GA Log notifier list before the VM is     actually destroyed, to fix a potential use-after-free   - While FOLL_WRITE was needed in the past to trigger CoW unsharing,     nowadays FOLL_LONGTERM does that already even without FOLL_WRITE,     and in fact, get_user_pages() actually disallows FOLL_WRITE     together with FOLL_LONGTERM. So don&apos;t pass FOLL_WRITE when     registering encrypted memory regions, i.e. when pinning SEV/SEV-ES     guest memory, to fix a regression with file-backed memory     introduced by KVM&apos;s (correct) usage of long-term pins     (This was reviewed by mm maintainers; for more information, see     commit ee1a586dd1fa &quot;KVM: SEV: Drop FOLL_WRITE for encrypted region     registration&quot;)   - Allocate full pages for SEV/SEV-ES {DE,EN}CRYPT ops on SNP-enabled     hosts to fix a data corruption issue due to the PSP driver     assigning to-be-written pages to firmware (as required by the SNP     specs)   - Unconditionally intercept ICBEP so that KVM generates the correct     guest RIP when handling an ICEBP-induced TASK_SWITCH #VMEXIT   - Harden the SNP &quot;populate&quot; ioctls against bad input, and to prepare     for supporting in-place private&lt;=&gt;shared conversion  Generic:   - Remove kvm_debugfs_dir if kvm_init() fails after creating KVM&apos;s     debugfs   - Add a per-VM bitmap to track which vCPU IDs have been &quot;claimed&quot; but     for which the vCPU isn&apos;t yet online, and use the bitmap to reject     duplicate IDs before calling into arch code. This allows arch code     to consume vcpu_id without having to worry about cross-vCPU     clobbering (at least s390 and x86 have had related bugs)   - Rework the so called &quot;prepare&quot; and &quot;invalidate&quot; guest_memfd hooks     to prepare for in-place private&lt;=&gt;shared conversion, and clean up a     few warts along the way  Selftests:   - Automatically allocate a full page for L2 guest stacks on x86     instead of requiring test-specific L1 guest code to carve out a     portion of the L1 stack for L2 usage, and to ensure the L2 stack     also adheres to the x86-64 calling convention ABI   - Add a selftest to verify {Guest,Host}-Only behavior in x86&apos;s     mediated PMU   - Clean up nested SVM&apos;s handling of GPRs on L2&lt;=&gt;L1 transitions,     reuse the functionality for nested VMX, and drop the ucall hack     that was fudging around the lack of GPR switching on nVMX   - Add a stress test to verify KVM doesn&apos;t clobber/drop #PF state,     e.g. CR2, across save/restore, including when L2 is active   - Add a test to verify KVM_CREATE_VM accepts exactly what is reported     by KVM_CAP_VM_TYPES   - Misc selftests fixes and cleanups   - Fix several issues with seeding the pRNG, and rework the pRNG APIs     to that the pRNG can be sanely used in host code, not just guest     code   - Add an IRQ test to validate virtual IRQ deliverty for IRQs wired up     via KVM_IRQFD + KVM_SET_GSI_ROUTING, with optional support for     triggering IRQs via writes to an assigned VFIO device   - Add syscall wrappers to assert success on a variety of pthreads and     CPU affinity APIs   - Set vCPU pthread affinity as early as possible to reduce contention     issues that were surfaced by PREEMPT_LAZY, which result in runtimes     of over a minute on large hosts, versus the expected ~5 seconds   - Rework the PMU counters test to run each testcase using a single VM     with many vCPUs for each sub-testcase, instead of using a unique VM     for each sub-testcase. This cuts the runtime by ~20x  Miscellaneous:   - MAINTAINERS updates for vfio-ap, guest_memfd, kvm-x86. Mostly     representing the status quo more accurately, but also... welcome     David Hildenbrand as guest_memfd reviewer!&quot;* tag &apos;for-linus&apos; of git://git.kernel.org/pub/scm/virt/kvm/kvm: (413 commits)  KVM: arm64: Validate GICv5 timer PPIs before claiming ownership  KVM: arm64: vgic: Reject out-of-range GICv5 PPI IDs  KVM: arm64: vgic: Prevent speculative SPI array underflow  KVM: arm64: vgic: Free gic_kvm_info on initialization failure  KVM: arm64: Avoid mismatched accesses to &apos;struct kvm_nvhe_init_params&apos;  s390/vfio-ap: Fix NULL deref in status_show() during queue probe  s390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed  s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap  s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove  s390/vfio-ap: Fix required lock not held during update of ap_matrix_mdev object  s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects  s390/vfio-ap: Fix dereference matrix_mdev-&gt;kvm without checking for NULL  s390/vfio-ap: Fix stale do_remove flag across iterations in vfio_ap_mdev_cfg_remove  RISC-V: KVM: fix vcpu vector context handling for kernel-mode vector  riscv: vector: allow non-preemptible kernel-mode vector with IRQs off  riscv: vector: refactor riscv_v_start_kernel_context  KVM: s390: gmap: Make prefix handling optional  KVM: s390: gmap: Make CMMA optional  KVM: s390: gmap: Make storage keys optional  KVM: s390: Prepare gmap for a second KVM implementation  ...

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Tue, 25 Aug 2026 20:48:04 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>e4fa246243083391a65a721dbbc340766668d829 - arm64: sysreg: Add BBM_3</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#e4fa246243083391a65a721dbbc340766668d829</link>
        <description>arm64: sysreg: Add BBM_3Add BBM_3 definition for ID_AA64MMFR2_EL1 register.Reviewed-by: Gavin Shan &lt;gshan@redhat.com&gt;Reviewed-by: Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;Signed-off-by: Linu Cherian &lt;linu.cherian@arm.com&gt;Signed-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Thu, 23 Jul 2026 06:40:31 +0200</pubDate>
        <dc:creator>Linu Cherian &lt;linu.cherian@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>9809bdf151e2e92981ee2bd45bde1e0477c933a5 - arm64: sysreg: Add HCRX_EL2 bits related to FEAT_NV3</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#9809bdf151e2e92981ee2bd45bde1e0477c933a5</link>
        <description>arm64: sysreg: Add HCRX_EL2 bits related to FEAT_NV3FEAT_NV3 introduces 4 new HCRX_EL2 control bits. Describe themin the sysreg file.Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;Reviewed-by: Joey Gouly &lt;joey.gouly@arm.com&gt;Link: https://patch.msgid.link/20260730071022.296811-15-maz@kernel.orgSigned-off-by: Oliver Upton &lt;oupton@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Thu, 30 Jul 2026 09:10:07 +0200</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7c81d7c4ef6e3d9d3c8796c1f0947a2716140f5f - arm64: sysreg: Add NVHCR_EL2 description as a mirror of HCR_EL2</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#7c81d7c4ef6e3d9d3c8796c1f0947a2716140f5f</link>
        <description>arm64: sysreg: Add NVHCR_EL2 description as a mirror of HCR_EL2FEAT_NV3 introduces a new register that contains the HCR_EL2 valueexposed to a NV guest. As such, it has the exact same layout asHCR_EL2.Describe NVHCR_EL2 as a mapping to HCR_EL2.Reviewed-by: Yuan Yao &lt;yaoyuan@linux.alibaba.com&gt;Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;Link: https://patch.msgid.link/20260730071022.296811-14-maz@kernel.orgSigned-off-by: Oliver Upton &lt;oupton@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Thu, 30 Jul 2026 09:10:06 +0200</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>fed0a1e87c283be0334f939879e890419a648f19 - KVM: arm64: Plumb HCRX_EL2.SRMASKEn in HCRX_EL2 sanitisation</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#fed0a1e87c283be0334f939879e890419a648f19</link>
        <description>KVM: arm64: Plumb HCRX_EL2.SRMASKEn in HCRX_EL2 sanitisationHCRX_EL2.SRMASKEn is a new bit enabling FEAT_SRMASK for a guest.We don&apos;t plan to support it any time soon, but it doesn&apos;t hurt toactively document it, specially as we are going to add more bitswe actually care about.Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;Link: https://patch.msgid.link/20260730071022.296811-6-maz@kernel.orgSigned-off-by: Oliver Upton &lt;oupton@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Thu, 30 Jul 2026 09:09:58 +0200</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>1441f717ab5c9b6b476effc8b62a57a39c27b809 - arm64: Update ID_AA64MMFR4_EL1 description to 2026-03 JSON release</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#1441f717ab5c9b6b476effc8b62a57a39c27b809</link>
        <description>arm64: Update ID_AA64MMFR4_EL1 description to 2026-03 JSON releaseID_AA64MMFR4_EL1 has gained a few fields and enum values in the pastfew months, so resync its definition with the 2026-03 JSON release.Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;Reviewed-by: Joey Gouly &lt;joey.gouly@arm.com&gt;Link: https://patch.msgid.link/20260730071022.296811-3-maz@kernel.orgSigned-off-by: Oliver Upton &lt;oupton@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Thu, 30 Jul 2026 09:09:55 +0200</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>6666336d8fe5f3f0cd3f8da2865ca78110a6e170 - arm64/sysreg: Fix BWE field encoding in ID_AA64DFR2_EL1</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#6666336d8fe5f3f0cd3f8da2865ca78110a6e170</link>
        <description>arm64/sysreg: Fix BWE field encoding in ID_AA64DFR2_EL1Commit 93d7356e4b30 (&quot;arm64: sysreg: Describe ID_AA64DFR2_EL1 fields&quot;)encodes the FEAT_BWE2 value of the BWE field as &apos;0b0002&apos;. Binaryliterals only accept the digits 0 and 1, so the intended value is 2,i.e. 0b0010.The macro generated by gen-sysreg.awk currently expands to	#define ID_AA64DFR2_EL1_BWE_FEAT_BWE2 UL(0b0002)is not legal C and would fail to compile if any in-tree code referencedit. At present no caller uses this enum value, so the kernel stillbuilds cleanly, but the bug is latent.Fix the typo by using the correct binary literal 0b0010.Cc: Bin Guo &lt;guobin@linux.alibaba.com&gt;Fixes: 93d7356e4b30 (&quot;arm64: sysreg: Describe ID_AA64DFR2_EL1 fields&quot;)Signed-off-by: Jia He &lt;justin.he@arm.com&gt;Reviewed-by: Mark Brown &lt;broonie@kernel.org&gt;Reviewed-by: Oliver Upton &lt;oupton@kernel.org&gt;Acked-by: Marc Zyngier &lt;maz@kernel.org&gt;Signed-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Wed, 01 Jul 2026 00:23:47 +0200</pubDate>
        <dc:creator>Jia He &lt;justin.he@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>61c19a9feb1d87156e46e38d7759f3ad23710e24 - Merge branch &apos;for-next/sysregs&apos; into for-next/core</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#61c19a9feb1d87156e46e38d7759f3ad23710e24</link>
        <description>Merge branch &apos;for-next/sysregs&apos; into for-next/core* for-next/sysregs:  arm64/sysreg: Add HDBSS related register information

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Sun, 14 Jun 2026 13:18:27 +0200</pubDate>
        <dc:creator>Will Deacon &lt;will@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>36a1d1726634f2e53eefaec32e116fad465b89cb - arm64: sysreg: Add FPCR and FPSR</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#36a1d1726634f2e53eefaec32e116fad465b89cb</link>
        <description>arm64: sysreg: Add FPCR and FPSRAdd sysreg definitions for FPCR and FPSR.Some versions of LLVM will refuse to assemble accesses to FPCR and FPSRunless the &quot;fp&quot; arch extension is enabled, which we don&apos;t currently dofor read_sysreg() and write_sysreg(). In general, handling featuredependencies would complicate read_sysreg() and write_sysreg(), and it&apos;ssimpler to use read_sysreg_s() and write_sysreg_s() instead, requiringsysreg definitions.The values used can be found in ARM ARM issue M.b:  https://developer.arm.com/documentation/ddi0487/mb/... in sections:* C5.2.8 (&quot;FPCR, Floating-point Control Register&quot;)* C5.2.10 (&quot;FPSR, Floating-point Status Register&quot;)Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;Reviewed-by: Mark Brown &lt;broonie@kernel.org&gt;Reviewed-by: Vladimir Murzin &lt;vladimir.murzin@arm.com&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Fuad Tabba &lt;tabba@google.com&gt;Cc: James Morse &lt;james.morse@arm.com&gt;Cc: Marc Zyngier &lt;maz@kernel.org&gt;Cc: Oliver Upton &lt;oupton@kernel.org&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Wed, 03 Jun 2026 13:06:22 +0200</pubDate>
        <dc:creator>Mark Rutland &lt;mark.rutland@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>72f7be0c2e303be591ace9312c51d22d7c2d6882 - arm64/sysreg: Add HDBSS related register information</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#72f7be0c2e303be591ace9312c51d22d7c2d6882</link>
        <description>arm64/sysreg: Add HDBSS related register informationThe ARM architecture added the HDBSS feature and descriptions ofrelated registers (HDBSSBR/HDBSSPROD) in the DDI0601(ID121123) version,add them to Linux.Signed-off-by: eillon &lt;yezhenyu2@huawei.com&gt;Signed-off-by: Tian Zheng &lt;zhengtian10@huawei.com&gt;Signed-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Wed, 25 Feb 2026 05:04:17 +0100</pubDate>
        <dc:creator>eillon &lt;yezhenyu2@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>01f492e1817e858d1712f2489d0afbaa552f417b - Merge tag &apos;for-linus&apos; of git://git.kernel.org/pub/scm/virt/kvm/kvm</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#01f492e1817e858d1712f2489d0afbaa552f417b</link>
        <description>Merge tag &apos;for-linus&apos; of git://git.kernel.org/pub/scm/virt/kvm/kvmPull kvm updates from Paolo Bonzini: &quot;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 &apos;remote&apos; 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 +     &apos;kvm-arm.mode=protected&apos;, 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&apos;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 &quot;easy&quot;, but &quot;easier&quot;)   - 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&apos;s headers that is included multiple times   - Reject SET_GUEST_DEBUG with -EBUSY if there&apos;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&apos;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 &quot;too large&quot; 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&apos;s APIs for detecting SEV+ guests so that VM-scoped     queries are required to hold kvm-&gt;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-&gt;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-&gt;arch.cr2 when updating vmcb12&apos;s CR2 on nested #VMEXIT     instead of vmcb02-&gt;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&apos;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&apos;t double     down on AMD&apos;s architectural but sketchy behavior of generating #GP     for &quot;unsupported&quot; 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&apos;t mark guest_memfd folios as accessed, as guest_memfd doesn&apos;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&apos;s will&quot;* tag &apos;for-linus&apos; 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-&gt;lock is held when querying SEV+ support  KVM: SEV: Document that checking for SEV+ guests when reclaiming memory is &quot;safe&quot;  KVM: SEV: Hide &quot;struct kvm_sev_info&quot; 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/tools/sysreg</description>
        <pubDate>Fri, 17 Apr 2026 16:18:03 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>480a9e57cceaf42db6ff874dbfe91de201935035 - Merge branches &apos;for-next/misc&apos;, &apos;for-next/tlbflush&apos;, &apos;for-next/ttbr-macros-cleanup&apos;, &apos;for-next/kselftest&apos;, &apos;for-next/feat_lsui&apos;, &apos;for-next/mpam&apos;, &apos;for-next/hotplug-batched-tlbi&apos;, &apos;for-next/bbml2-fixes&apos;, &apos;for-next/sysreg&apos;, &apos;for-next/generic-entry&apos; and &apos;for-next/acpi&apos;, remote-tracking branches &apos;arm64/for-next/perf&apos; and &apos;arm64/for-next/read-once&apos; into for-next/core</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#480a9e57cceaf42db6ff874dbfe91de201935035</link>
        <description>Merge branches &apos;for-next/misc&apos;, &apos;for-next/tlbflush&apos;, &apos;for-next/ttbr-macros-cleanup&apos;, &apos;for-next/kselftest&apos;, &apos;for-next/feat_lsui&apos;, &apos;for-next/mpam&apos;, &apos;for-next/hotplug-batched-tlbi&apos;, &apos;for-next/bbml2-fixes&apos;, &apos;for-next/sysreg&apos;, &apos;for-next/generic-entry&apos; and &apos;for-next/acpi&apos;, remote-tracking branches &apos;arm64/for-next/perf&apos; and &apos;arm64/for-next/read-once&apos; into for-next/core* arm64/for-next/perf:  : Perf updates  perf/arm-cmn: Fix resource_size_t printk specifier in arm_cmn_init_dtc()  perf/arm-cmn: Fix incorrect error check for devm_ioremap()  perf: add NVIDIA Tegra410 C2C PMU  perf: add NVIDIA Tegra410 CPU Memory Latency PMU  perf/arm_cspmu: nvidia: Add Tegra410 PCIE-TGT PMU  perf/arm_cspmu: nvidia: Add Tegra410 PCIE PMU  perf/arm_cspmu: Add arm_cspmu_acpi_dev_get  perf/arm_cspmu: nvidia: Add Tegra410 UCF PMU  perf/arm_cspmu: nvidia: Rename doc to Tegra241  perf/arm-cmn: Stop claiming entire iomem region  arm64: cpufeature: Use pmuv3_implemented() function  arm64: cpufeature: Make PMUVer and PerfMon unsigned  KVM: arm64: Read PMUVer as unsigned* arm64/for-next/read-once:  : Fixes for __READ_ONCE() with CONFIG_LTO=y  arm64, compiler-context-analysis: Permit alias analysis through __READ_ONCE() with CONFIG_LTO=y  arm64: Optimize __READ_ONCE() with CONFIG_LTO=y* for-next/misc:  : Miscellaneous cleanups/fixes  arm64: rsi: use linear-map alias for realm config buffer  arm64: Kconfig: fix duplicate word in CMDLINE help text  arm64: mte: Skip TFSR_EL1 checks and barriers in synchronous tag check mode  arm64/hwcap: Generate the KERNEL_HWCAP_ definitions for the hwcaps  arm64: kexec: Remove duplicate allocation for trans_pgd  arm64: mm: Use generic enum pgtable_level  arm64: scs: Remove redundant save/restore of SCS SP on entry to/from EL0  arm64: remove ARCH_INLINE_** for-next/tlbflush:  : Refactor the arm64 TLB invalidation API and implementation  arm64: mm: __ptep_set_access_flags must hint correct TTL  arm64: mm: Provide level hint for flush_tlb_page()  arm64: mm: Wrap flush_tlb_page() around __do_flush_tlb_range()  arm64: mm: More flags for __flush_tlb_range()  arm64: mm: Refactor __flush_tlb_range() to take flags  arm64: mm: Refactor flush_tlb_page() to use __tlbi_level_asid()  arm64: mm: Simplify __flush_tlb_range_limit_excess()  arm64: mm: Simplify __TLBI_RANGE_NUM() macro  arm64: mm: Re-implement the __flush_tlb_range_op macro in C  arm64: mm: Inline __TLBI_VADDR_RANGE() into __tlbi_range()  arm64: mm: Push __TLBI_VADDR() into __tlbi_level()  arm64: mm: Implicitly invalidate user ASID based on TLBI operation  arm64: mm: Introduce a C wrapper for by-range TLB invalidation  arm64: mm: Re-implement the __tlbi_level macro as a C function* for-next/ttbr-macros-cleanup:  : Cleanups of the TTBR1_* macros  arm64/mm: Directly use TTBRx_EL1_CnP  arm64/mm: Directly use TTBRx_EL1_ASID_MASK  arm64/mm: Describe TTBR1_BADDR_4852_OFFSET* for-next/kselftest:  : arm64 kselftest updates  selftests/arm64: Implement cmpbr_sigill() to hwcap test* for-next/feat_lsui:  : Futex support using FEAT_LSUI instructions to avoid toggling PAN  arm64: armv8_deprecated: Disable swp emulation when FEAT_LSUI present  arm64: Kconfig: Add support for LSUI  KVM: arm64: Use CAST instruction for swapping guest descriptor  arm64: futex: Support futex with FEAT_LSUI  arm64: futex: Refactor futex atomic operation  KVM: arm64: kselftest: set_id_regs: Add test for FEAT_LSUI  KVM: arm64: Expose FEAT_LSUI to guests  arm64: cpufeature: Add FEAT_LSUI* for-next/mpam: (40 commits)  : Expose MPAM to user-space via resctrl:  :  - Add architecture context-switch and hiding of the feature from KVM.  :  - Add interface to allow MPAM to be exposed to user-space using resctrl.  :  - Add errata workaoround for some existing platforms.  :  - Add documentation for using MPAM and what shape of platforms can use resctrl  arm64: mpam: Add initial MPAM documentation  arm_mpam: Quirk CMN-650&apos;s CSU NRDY behaviour  arm_mpam: Add workaround for T241-MPAM-6  arm_mpam: Add workaround for T241-MPAM-4  arm_mpam: Add workaround for T241-MPAM-1  arm_mpam: Add quirk framework  arm_mpam: resctrl: Call resctrl_init() on platforms that can support resctrl  arm64: mpam: Select ARCH_HAS_CPU_RESCTRL  arm_mpam: resctrl: Add empty definitions for assorted resctrl functions  arm_mpam: resctrl: Update the rmid reallocation limit  arm_mpam: resctrl: Add resctrl_arch_rmid_read()  arm_mpam: resctrl: Allow resctrl to allocate monitors  arm_mpam: resctrl: Add support for csu counters  arm_mpam: resctrl: Add monitor initialisation and domain boilerplate  arm_mpam: resctrl: Add kunit test for control format conversions  arm_mpam: resctrl: Add support for &apos;MB&apos; resource  arm_mpam: resctrl: Wait for cacheinfo to be ready  arm_mpam: resctrl: Add rmid index helpers  arm_mpam: resctrl: Convert to/from MPAMs fixed-point formats  arm_mpam: resctrl: Hide CDP emulation behind CONFIG_EXPERT  ...* for-next/hotplug-batched-tlbi:  : arm64/mm: Enable batched TLB flush in unmap_hotplug_range()  arm64/mm: Reject memory removal that splits a kernel leaf mapping  arm64/mm: Enable batched TLB flush in unmap_hotplug_range()* for-next/bbml2-fixes:  : Fixes for realm guest and BBML2_NOABORT  arm64: mm: Remove pmd_sect() and pud_sect()  arm64: mm: Handle invalid large leaf mappings correctly  arm64: mm: Fix rodata=full block mapping support for realm guests* for-next/sysreg:  : arm64 sysreg updates  arm64/sysreg: Update ID_AA64SMFR0_EL1 description to DDI0601 2025-12  arm64/sysreg: Update ID_AA64ZFR0_EL1 description to DDI0601 2025-12  arm64/sysreg: Update ID_AA64FPFR0_EL1 description to DDI0601 2025-12  arm64/sysreg: Update ID_AA64ISAR2_EL1 description to DDI0601 2025-12  arm64/sysreg: Update ID_AA64ISAR0_EL1 description to DDI0601 2025-12  arm64/sysreg: Update SMIDR_EL1 to DDI0601 2025-06* for-next/generic-entry:  : More arm64 refactoring towards using the generic entry code  arm64: Check DAIF (and PMR) at task-switch time  arm64: entry: Use split preemption logic  arm64: entry: Use irqentry_{enter_from,exit_to}_kernel_mode()  arm64: entry: Consistently prefix arm64-specific wrappers  arm64: entry: Don&apos;t preempt with SError or Debug masked  entry: Split preemption from irqentry_exit_to_kernel_mode()  entry: Split kernel mode logic from irqentry_{enter,exit}()  entry: Move irqentry_enter() prototype later  entry: Remove local_irq_{enable,disable}_exit_to_user()  entry: Fix stale comment for irqentry_enter()* for-next/acpi:  : arm64 ACPI updates  ACPI: AGDI: fix missing newline in error message

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Fri, 10 Apr 2026 15:22:24 +0200</pubDate>
        <dc:creator>Catalin Marinas &lt;catalin.marinas@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>306736fd515565c6c4787dc55aba890ebce2dc45 - arm64/sysreg: Update ID_AA64SMFR0_EL1 description to DDI0601 2025-12</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#306736fd515565c6c4787dc55aba890ebce2dc45</link>
        <description>arm64/sysreg: Update ID_AA64SMFR0_EL1 description to DDI0601 2025-12The 2025 extensions add FEAT_SME2P3, including LUT6.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 02 Mar 2026 23:53:21 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>bf56250f34a40d83252e1cbc3b41955df7dc11b1 - arm64/sysreg: Update ID_AA64ZFR0_EL1 description to DDI0601 2025-12</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#bf56250f34a40d83252e1cbc3b41955df7dc11b1</link>
        <description>arm64/sysreg: Update ID_AA64ZFR0_EL1 description to DDI0601 2025-12The 2025 extensions add FEAT_SVE2P3 and FEAT_SVE_B16MM.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 02 Mar 2026 23:53:20 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>d74576b51ba6d3a7f1f321b57ad8736f73a5074d - arm64/sysreg: Update ID_AA64FPFR0_EL1 description to DDI0601 2025-12</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#d74576b51ba6d3a7f1f321b57ad8736f73a5074d</link>
        <description>arm64/sysreg: Update ID_AA64FPFR0_EL1 description to DDI0601 2025-12The 2025 extensions add FEAT_F16MM and adjust some of the RES0 bits to beRAZ instead as a placeholder for future extensions.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 02 Mar 2026 23:53:19 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>bb5e1e540501f068f888dca8951128d682f5ff44 - arm64/sysreg: Update ID_AA64ISAR2_EL1 description to DDI0601 2025-12</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#bb5e1e540501f068f888dca8951128d682f5ff44</link>
        <description>arm64/sysreg: Update ID_AA64ISAR2_EL1 description to DDI0601 2025-12The 2025 extensions update the LUT field for new instructions added bySVE and SME 2.3, there is no separate FEAT_ feature for these.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 02 Mar 2026 23:53:18 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b964aa8d68f7705932357483d35d82067bd755c3 - arm64/sysreg: Update ID_AA64ISAR0_EL1 description to DDI0601 2025-12</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#b964aa8d68f7705932357483d35d82067bd755c3</link>
        <description>arm64/sysreg: Update ID_AA64ISAR0_EL1 description to DDI0601 2025-12The 2025 extensions add FEAT_F16F32DOT and FEAT_F16F32MM.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Mon, 02 Mar 2026 23:53:17 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>85b6f920a8691d96441da9da7fc55ec93b906fe6 - arm64/sysreg: Update SMIDR_EL1 to DDI0601 2025-06</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#85b6f920a8691d96441da9da7fc55ec93b906fe6</link>
        <description>arm64/sysreg: Update SMIDR_EL1 to DDI0601 2025-06Update the definition of SMIDR_EL1 in the sysreg definition to reflect theinformation in DD0601 2025-06. This includes somewhat more generic ways ofdescribing the sharing of SMCUs, more information on supported prioritiesand provides additional resolution for describing affinity groups.Reviewed-by: Fuad Tabba &lt;tabba@google.com&gt;Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Reviewed-by: Alex Benn&#233;e &lt;alex.bennee@linaro.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Fri, 06 Mar 2026 18:00:53 +0100</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>77acae60be60adddf33e4c7e9cf73291f64fb9e8 - arm64: Fix field references for ICH_PPI_DVIR[01]_EL2</title>
        <link>http://kernelsources.org:8080/source/history/linux/arch/arm64/tools/sysreg#77acae60be60adddf33e4c7e9cf73291f64fb9e8</link>
        <description>arm64: Fix field references for ICH_PPI_DVIR[01]_EL2The ICH_PPI_DVIR[01]_EL2 registers should refer to the ICH_PPI_DVIRx_EL2fields, instead of ICH_PPI_DVIx_EL2.Reviewed-by: Sascha Bischoff &lt;sascha.bischoff@arm.com&gt;Fixes: 2808a8337078f (&quot;arm64/sysreg: Add remaining GICv5 ICC_ &amp; ICH_ sysregs for KVM support&quot;)Link: https://sashiko.dev/#/patchset/20260319154937.3619520-1-sascha.bischoff%40arm.comLink: https://patch.msgid.link/20260401103611.357092-4-maz@kernel.orgSigned-off-by: Marc Zyngier &lt;maz@kernel.org&gt;

            List of files:
            /linux/arch/arm64/tools/sysreg</description>
        <pubDate>Wed, 01 Apr 2026 12:35:58 +0200</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
