public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, gleb@redhat.com,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: [uq/master patch 1/2] kvm-all.c: use recommended max vcpus limit
Date: Mon, 12 Aug 2013 16:56:30 -0300	[thread overview]
Message-ID: <20130812195730.079414823@redhat.com> (raw)
In-Reply-To: 20130812195629.350634011@redhat.com

[-- Attachment #1: kvm-all-use-cap-nr-vcpus-first --]
[-- Type: text/plain, Size: 940 bytes --]

Commit 8c3ba334f8588e1d5099f8602cf01897720e0eca, "KVM: x86: Raise the
hard VCPU count limit", upstream introduced the notion of a recommended
vcpu max limit.

Switch the order so the recommended vcpu max limit is used instead of
the actual max vcpu limit.

Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

Index: qemu/kvm-all.c
===================================================================
--- qemu.orig/kvm-all.c
+++ qemu/kvm-all.c
@@ -1321,11 +1321,11 @@ static int kvm_max_vcpus(KVMState *s)
      * procedure from the kernel API documentation to cope with
      * older kernels that may be missing capabilities.
      */
-    ret = kvm_check_extension(s, KVM_CAP_MAX_VCPUS);
+    ret = kvm_check_extension(s, KVM_CAP_NR_VCPUS);
     if (ret) {
         return ret;
     }
-    ret = kvm_check_extension(s, KVM_CAP_NR_VCPUS);
+    ret = kvm_check_extension(s, KVM_CAP_MAX_VCPUS);
     if (ret) {
         return ret;
     }



  reply	other threads:[~2013-08-12 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 19:56 [uq/master patch 0/2] kvm max vcpu limit fixes Marcelo Tosatti
2013-08-12 19:56 ` Marcelo Tosatti [this message]
2013-08-18 15:28   ` [uq/master patch 1/2] kvm-all.c: use recommended max vcpus limit Paolo Bonzini
2013-08-18 16:15     ` Marcelo Tosatti
2013-08-12 19:56 ` [uq/master patch 2/2] kvm-all.c: max_cpus should not exceed KVM vcpu limit Marcelo Tosatti
2013-08-20 16:44   ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130812195730.079414823@redhat.com \
    --to=mtosatti@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox