summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorGeoff Levand <geoff@infradead.org>2013-01-31 12:06:08 -0800
committerMarcelo Tosatti <mtosatti@redhat.com>2013-02-05 22:48:50 -0200
commit4293b5e5a68074431cafa74d549c1327ba1d0deb (patch)
tree9ac414b3df6b20246368618bd3a741ada36156d0 /Documentation
parent834be0d83f9451573e6fadb381fe0714211c7e90 (diff)
downloadop-kernel-dev-4293b5e5a68074431cafa74d549c1327ba1d0deb.zip
op-kernel-dev-4293b5e5a68074431cafa74d549c1327ba1d0deb.tar.gz
KVM: Remove duplicate text in api.txt
Signed-off-by: Geoff Levand <geoff@infradead.org> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/virtual/kvm/api.txt13
1 files changed, 0 insertions, 13 deletions
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
index 0e03b19..c2534c3 100644
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@ -219,19 +219,6 @@ 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.
-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.
-
For virtual cpus that have been created with S390 user controlled virtual
machines, the resulting vcpu fd can be memory mapped at page offset
KVM_S390_SIE_PAGE_OFFSET in order to obtain a memory map of the virtual
OpenPOWER on IntegriCloud