Skip to content

RFC Target CPU=Host implementation for KVM ARM/ARM64

Will Deacon linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 3 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64
Quoted 27 lines · Alexander Graf
Quoted 15 lines · Anup Patel
Quoted 14 lines · Peter Maydell
Quoted 12 lines · Anup Patel

It will be very useful for user space if it has a method for specifying KVM ARM/ARM64 to give a VCPU with target type suitable to underlying host but with particular set of features.

In other words, user space might not be interested in having a particular target type for VCPU but it will certainely want particular set of features in the VCPU.

The patch tries to implement above described method of specifying VCPU target CPU=Host from user space by extending the KVM_ARM_VCPU_INIT ioctl and having a dummy target KVM_ARM_TARGET_HOST which means Target CPU same as (or suitable to) underlying host.

Quoted 8 lines
Quoted 4 lines

I thought the consensus on the call last week was
to have an ioctl for "get best CPU for this host"
and then for userspace to pass that value to
VCPU_INIT ?

I had considered having a separate ioctl for "get best CPU for this host" (as per KVM call minutes) but the same thing is possible with existing KVM_ARM_VCPU_INIT so why not extend this ioctl. Also, I was finding

Quoted 6 lines

Because it means that everything as of the INIT call is reproducible by user space. There is no way the kernel can do magic behind our back to create a vcpu that user space couldn't create the same way on a different host when you want to live migrate.

Quoted 2 lines

it hard to come up with a use case where having a separate ioctl for "get best CPU for this host" would be better for user space.

It can store it and migrate it as part of its migration protocol (probably hard for QEMU's current work flow, but that's QEMU's issue).

It's also better from the point of view of devicetree generation. For example, kvmtool needs to generate the correct architected timer interrupt numbers for the target CPU, so munging this into KVM_ARM_VCPU_INIT means we have to go off and figure out the host CPU separately anyway.

Will