Skip to contentSkip to conversation

linux-next: manual merge of the kvm-x86 tree with the kvm tree

PATCH Mark Brown 2 participants 2 messages Oct 20

Subsystems (4)
lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

Hi all,

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

tools/testing/selftests/kvm/x86/nested_x2apic_test.c

between commit:

994489f04ebbb ("Merge tag 'kvm-x86-selftests-7.4' of https://github.com/kvm-x86/linux into HEAD")

from the kvm tree and commit:

8b0aa41839602 ("Merge branch 'selftests'")

from the kvm-x86 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.

tools/testing/selftests/kvm/x86/nested_x2apic_test.c +0 -0
diff --combined tools/testing/selftests/kvm/x86/nested_x2apic_test.c
index bba301cfc0b5a,2ae698c9aa1ce..0000000000000
@@@ -86,7 -86,7 +86,7 @@@ static void l1_vmx_code(struct vmx_page
  		   SECONDARY_EXEC_APIC_REGISTER_VIRT |
  		   SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY;
  	control &= (rdmsr(MSR_IA32_VMX_PROCBASED_CTLS2) >> 32);
- 	vmwrite(SECONDARY_VM_EXEC_CONTROL, control), 0;
+ 	vmwrite(SECONDARY_VM_EXEC_CONTROL, control);
  
  	vmlaunch();
  	GUEST_ASSERT_EQ(vmread(VM_EXIT_REASON), EXIT_REASON_CPUID);
maintainer
#1 lore raw

Il mar 20 ott 2026, 14:27 Mark Brown <[email protected]> ha scritto:

Quoted 11 lines

Hi all,

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

tools/testing/selftests/kvm/x86/nested_x2apic_test.c

between commit:

994489f04ebbb ("Merge tag 'kvm-x86-selftests-7.4' of https://github.com/kvm-x86/linux into HEAD")

Quoted 7 lines

from the kvm tree and commit:

8b0aa41839602 ("Merge branch 'selftests'")

from the kvm-x86 tree.

I fixed it up (see below) and can carry the fix as necessary.

Oops, my (harmless) mistake in solving the conflict. I will add a fixup patch to kvm/next.

Paolo