Commit 36442687 authored by Avi Kivity's avatar Avi Kivity

KVM: Restore missing powerpc API docs

Commit 371fefd6 lost a doc hunk somehow, restore it.
Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
parent 58fbbf26
...@@ -200,6 +200,19 @@ allocation of vcpu ids. For example, if userspace wants ...@@ -200,6 +200,19 @@ allocation of vcpu ids. For example, if userspace wants
single-threaded guest vcpus, it should make all vcpu ids be a multiple single-threaded guest vcpus, it should make all vcpu ids be a multiple
of the number of vcpus per vcore. of the number of vcpus per vcore.
On powerpc using book3s_hv mode, the vcpus are mapped onto virtual
threads in one or more virtual CPU cores. (This is because the
hardware requires all the hardware threads in a CPU core to be in the
same partition.) The KVM_CAP_PPC_SMT capability indicates the number
of vcpus per virtual core (vcore). The vcore id is obtained by
dividing the vcpu id by the number of vcpus per vcore. The vcpus in a
given vcore will always be in the same physical core as each other
(though that might be a different physical core from time to time).
Userspace can control the threading (SMT) mode of the guest by its
allocation of vcpu ids. For example, if userspace wants
single-threaded guest vcpus, it should make all vcpu ids be a multiple
of the number of vcpus per vcore.
4.8 KVM_GET_DIRTY_LOG (vm ioctl) 4.8 KVM_GET_DIRTY_LOG (vm ioctl)
Capability: basic Capability: basic
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment