From 03d1e5650b81db94d4e0dab18fe0419db9862eae Mon Sep 17 00:00:00 2001 From: Pekka Enberg Date: Mon, 9 May 2011 22:48:54 +0300 Subject: [PATCH] --- yaml --- r: 248109 b: refs/heads/master c: 76d25402dfc972a135a656613736fe3602045a95 h: refs/heads/master i: 248107: 71e24985ea1fa207eb0e0f7261645161d8a6b07f v: v3 --- [refs] | 2 +- trunk/Documentation/kvm/api.txt | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index b4aa8eade4aa..01f293e22c18 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 8fa2206821953a50a3a02ea33fcfb3ced2fd9997 +refs/heads/master: 76d25402dfc972a135a656613736fe3602045a95 diff --git a/trunk/Documentation/kvm/api.txt b/trunk/Documentation/kvm/api.txt index f64c41f8ba61..42542eb802ca 100644 --- a/trunk/Documentation/kvm/api.txt +++ b/trunk/Documentation/kvm/api.txt @@ -175,7 +175,10 @@ Parameters: vcpu id (apic id on x86) Returns: vcpu fd on success, -1 on error This API adds a vcpu to a virtual machine. The vcpu id is a small integer -in the range [0, max_vcpus). +in the range [0, max_vcpus). You can use KVM_CAP_NR_VCPUS of the +KVM_CHECK_EXTENSION ioctl() to determine the value for max_vcpus at run-time. +If the KVM_CAP_NR_VCPUS does not exist, you should assume that max_vcpus is 4 +cpus max. 4.8 KVM_GET_DIRTY_LOG (vm ioctl)