linux-kernel - linux-next: manual merge of the kvm-riscv tree with the kvm-arm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20250521164814.3fddb821@canb.auug.org.au>
Date: Wed, 21 May 2025 16:48:14 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Anup Patel <anup@...infault.org>, Christoffer Dall
 <cdall@...columbia.edu>, Marc Zyngier <maz@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Radim Krčmář
 <rkrcmar@...tanamicro.com>
Subject: linux-next: manual merge of the kvm-riscv tree with the kvm-arm
 tree

Hi all,

Today's linux-next merge of the kvm-riscv tree got a conflict in:

  include/uapi/linux/kvm.h

between commit:

  a7484c80e5ca ("KVM: arm64: Allow userspace to request KVM_ARM_VCPU_EL2*")

from the kvm-arm tree and commit:

  5b9db9c16f42 ("RISC-V: KVM: add KVM_CAP_RISCV_MP_STATE_RESET")

from the kvm-riscv tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc include/uapi/linux/kvm.h
index e6ed559d9091,454b7d4a0448..000000000000
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@@ -931,8 -930,7 +931,9 @@@ struct kvm_enable_cap 
  #define KVM_CAP_X86_APIC_BUS_CYCLES_NS 237
  #define KVM_CAP_X86_GUEST_MODE 238
  #define KVM_CAP_ARM_WRITABLE_IMP_ID_REGS 239
 -#define KVM_CAP_RISCV_MP_STATE_RESET 240
 +#define KVM_CAP_ARM_EL2 240
 +#define KVM_CAP_ARM_EL2_E2H0 241
++#define KVM_CAP_RISCV_MP_STATE_RESET 242
  
  struct kvm_irq_routing_irqchip {
  	__u32 irqchip;

Content of type "application/pgp-signature" skipped