From: Matt Evans <matt@ozlabs.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: KVM list <kvm@vger.kernel.org>
Subject: [PATCH] kvm tools: Correctly limit nrcpus to max_cpus
Date: Thu, 08 Dec 2011 13:47:06 +1100 [thread overview]
Message-ID: <4EE0252A.3020806@ozlabs.org> (raw)
Fix a typo where kvm->nrcpus was set, then immediately overwritten with
older value.
Signed-off-by: Matt Evans <matt@ozlabs.org>
---
tools/kvm/builtin-run.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index cbf8777..84db7ea 100644
--- a/tools/kvm/builtin-run.c
+++ b/tools/kvm/builtin-run.c
@@ -820,7 +820,7 @@ int kvm_cmd_run(int argc, const char **argv, const char *prefix)
if (nrcpus > max_cpus) {
printf(" # Limit the number of CPUs to %d\n", max_cpus);
- kvm->nrcpus = max_cpus;
+ nrcpus = max_cpus;
} else if (nrcpus > recommended_cpus) {
printf(" # Warning: The maximum recommended amount of VCPUs"
" is %d\n", recommended_cpus);
--
1.7.0.4
reply other threads:[~2011-12-08 2:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EE0252A.3020806@ozlabs.org \
--to=matt@ozlabs.org \
--cc=kvm@vger.kernel.org \
--cc=penberg@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).