RFC Target CPU=Host implementation for KVM ARM/ARM64
Get series with b4
b4 am [email protected]Versions newest first
- 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.
Cover letter [RFC PATCH 0/3] Target CPU=Host implementation for KVM ARM/ARM64
Quoted 19 lines · Anup Patel
Quoted 18 lines · Will Deacon
Quoted 16 lines · Anup Patel
Quoted 11 lines · Will Deacon
Quoted 5 lines · Alexander Graf
Quoted 2 lines · Anup Patel
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_INITmeans we have to go off and figure out the host CPU separately anyway.Please look at the patch carefully we are returning VCPU target type back to user space so, you can generate correct architected timer interrupt numbers for the target CPU.
Quoted 8 lines
Quoted 5 lines
I did look at the patch, but I also looked at the overriding consensus in the feedback saying that you can't change the direction of the ioctl, so that would require what I said above.
Will
Instead of arguing more, I'll save everyone's time and revise this patch as needed by everyone.
Cheers :)
Will