Skip to content

Conversation

@ianm-nv
Copy link

@ianm-nv ianm-nv commented Dec 5, 2025

The KVM_CAP_ARM_RME capability number changed between Linux kernel versions 6.16 and 6.17 (from 243 to 244). This change adds runtime detection of the host kernel version to ensure QEMU remains compatible with both kernel versions during the transition period.

The implementation:

  • Defaults to KVM_CAP_ARM_RME (244) from the updated headers
  • Detects kernel 6.16 at runtime and uses the previous value (243)
  • Applies the correct capability number to all RME-related ioctls

This allows the same QEMU binary to work correctly on hosts running either kernel version.

Testing was successful on CCA hardware with both the 6.16 and 6.17 kernel.

The KVM_CAP_ARM_RME capability number changed between Linux kernel
versions 6.16 and 6.17 (from 243 to 244). This change adds runtime
detection of the host kernel version to ensure QEMU remains compatible
with both kernel versions during the transition period.

The implementation:
- Defaults to KVM_CAP_ARM_RME (244) from the updated headers
- Detects kernel 6.16 at runtime and uses the previous value (243)
- Applies the correct capability number to all RME-related ioctls

This allows the same QEMU binary to work correctly on hosts running
either kernel version.

Signed-off-by: Shanker Donthineni <sdonthineni@nvidia.com>
Signed-off-by: Ian May <ianm@nvidia.com>
@nvmochs
Copy link
Collaborator

nvmochs commented Dec 5, 2025

I confirmed all the kvm_vm_enable_cap using KVM_CAP_ARM_RME have been converted to use the variable instead. The logic for kernel detection looks good.

Acked-by: Matthew R. Ochs <mochs@nvidia.com>

Copy link

@NathanChenNVIDIA NathanChenNVIDIA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acked-by: Nathan Chen nathanc@nvidia.com

@nvmochs
Copy link
Collaborator

nvmochs commented Dec 5, 2025

Merged, closing PR.

@nvmochs nvmochs closed this Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants