f9940416f1
It goes without saying, but it is probably better to spell it out: If userspace tries to restore and VM, but creates vcpus and/or RDs in a different order, the vcpu/RD mapping will be different. Yes, our API is an ugly piece of crap and I can't believe that we missed this. If we want to relax the above, we'll need to define a new userspace API that allows the mapping to be specified, rather than relying on the kernel to perform the mapping on its own. Reviewed-by: Zenghui Yu <yuzenghui@huawei.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20230927090911.3355209-12-maz@kernel.org Signed-off-by: Oliver Upton <oliver.upton@linux.dev> |
||
|---|---|---|
| .. | ||
| README | ||
| arm-vgic-its.rst | ||
| arm-vgic-v3.rst | ||
| arm-vgic.rst | ||
| index.rst | ||
| mpic.rst | ||
| s390_flic.rst | ||
| vcpu.rst | ||
| vfio.rst | ||
| vm.rst | ||
| xics.rst | ||
| xive.rst | ||
README
This directory contains specific device bindings for KVM_CAP_DEVICE_CTRL.