diff options
| author | Marc Zyngier <maz@kernel.org> | 2023-09-27 10:09:11 +0100 |
|---|---|---|
| committer | Oliver Upton <oliver.upton@linux.dev> | 2023-09-30 18:15:44 +0000 |
| commit | f9940416f193d148dd7ad7498ce4f40c83d12e7a (patch) | |
| tree | 5afc552517fcfec5f4fd03a68cc2f16ab6dd6d1d /include/kvm | |
| parent | b5daffb120bb60f974ae1a5589160b05c98e00e5 (diff) | |
KVM: arm64: Clarify the ordering requirements for vcpu/RD creation
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>
Diffstat (limited to 'include/kvm')
0 files changed, 0 insertions, 0 deletions