* linux-next: manual merge of the arm64 tree with the kvm-arm tree
@ 2026-03-27 18:44 Mark Brown
2026-04-01 11:01 ` Catalin Marinas
0 siblings, 1 reply; 2+ messages in thread
From: Mark Brown @ 2026-03-27 18:44 UTC (permalink / raw)
To: Catalin Marinas, Will Deacon
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Marc Zyngier,
Yeoreum Yun, Zenghui Yu
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Hi all,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm64/kvm/at.c
between commit:
0496acc42fb51e ("KVM: arm64: Fix the descriptor address in __kvm_at_swap_desc()")
from the kvm-arm tree and commit:
16dbe77a5be2de ("KVM: arm64: Use CAST instruction for swapping guest descriptor")
from the arm64 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.
diff --cc arch/arm64/kvm/at.c
index a024d9a770dc74,1adf88a5732840..00000000000000
--- a/arch/arm64/kvm/at.c
+++ b/arch/arm64/kvm/at.c
@@@ -1753,8 -1785,10 +1783,10 @@@ int __kvm_at_swap_desc(struct kvm *kvm
if (!writable)
return -EPERM;
- ptep = (u64 __user *)hva + offset;
+ ptep = (void __user *)hva + offset;
- if (cpus_have_final_cap(ARM64_HAS_LSE_ATOMICS))
+ if (cpus_have_final_cap(ARM64_HAS_LSUI))
+ r = __lsui_swap_desc(ptep, old, new);
+ else if (cpus_have_final_cap(ARM64_HAS_LSE_ATOMICS))
r = __lse_swap_desc(ptep, old, new);
else
r = __llsc_swap_desc(ptep, old, new);
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: manual merge of the arm64 tree with the kvm-arm tree
2026-03-27 18:44 linux-next: manual merge of the arm64 tree with the kvm-arm tree Mark Brown
@ 2026-04-01 11:01 ` Catalin Marinas
0 siblings, 0 replies; 2+ messages in thread
From: Catalin Marinas @ 2026-04-01 11:01 UTC (permalink / raw)
To: Mark Brown
Cc: Will Deacon, Linux Kernel Mailing List, Linux Next Mailing List,
Marc Zyngier, Yeoreum Yun, Zenghui Yu
On Fri, Mar 27, 2026 at 06:44:58PM +0000, Mark Brown wrote:
> diff --cc arch/arm64/kvm/at.c
> index a024d9a770dc74,1adf88a5732840..00000000000000
> --- a/arch/arm64/kvm/at.c
> +++ b/arch/arm64/kvm/at.c
> @@@ -1753,8 -1785,10 +1783,10 @@@ int __kvm_at_swap_desc(struct kvm *kvm
> if (!writable)
> return -EPERM;
>
> - ptep = (u64 __user *)hva + offset;
> + ptep = (void __user *)hva + offset;
> - if (cpus_have_final_cap(ARM64_HAS_LSE_ATOMICS))
> + if (cpus_have_final_cap(ARM64_HAS_LSUI))
> + r = __lsui_swap_desc(ptep, old, new);
> + else if (cpus_have_final_cap(ARM64_HAS_LSE_ATOMICS))
> r = __lse_swap_desc(ptep, old, new);
> else
> r = __llsc_swap_desc(ptep, old, new);
It looks fine. Thanks Mark.
--
Catalin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-04-01 11:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-27 18:44 linux-next: manual merge of the arm64 tree with the kvm-arm tree Mark Brown
2026-04-01 11:01 ` Catalin Marinas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox