From: Andrew Jones <drjones@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, ehabkost@redhat.com
Subject: [Qemu-devel] [PATCH 3/3] vl: warn on topology <-> maxcpus mismatch
Date: Fri, 7 Nov 2014 17:04:40 +0100 [thread overview]
Message-ID: <1415376280-14130-4-git-send-email-drjones@redhat.com> (raw)
In-Reply-To: <1415376280-14130-1-git-send-email-drjones@redhat.com>
Start guiding users towards making sure their topology supports the
maximum number of cpus they wish to support. A future patch series
will enforce this for new machine types.
Signed-off-by: Andrew Jones <drjones@redhat.com>
---
vl.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/vl.c b/vl.c
index c62fe29aa8075..72ffbffd858c5 100644
--- a/vl.c
+++ b/vl.c
@@ -1313,6 +1313,13 @@ static void smp_parse(QemuOpts *opts)
}
max_cpus = qemu_opt_get_number(opts, "maxcpus", 0);
+ max_cpus = max_cpus ?: cpus;
+
+ if (sockets * cores * threads != max_cpus) {
+ fprintf(stderr, "cpu topology: warning: "
+ "sockets (%u) * cores (%u) * threads (%u) != max_cpus (%u)\n",
+ sockets, cores, threads, max_cpus);
+ }
smp_cpus = cpus;
smp_cores = cores;
--
1.9.3
next prev parent reply other threads:[~2014-11-07 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 16:04 [Qemu-devel] [PATCH 0/3] vl: smp_parse sanity checks Andrew Jones
2014-11-07 16:04 ` [Qemu-devel] [PATCH 1/3] vl: fix max_cpus check Andrew Jones
2014-11-07 16:58 ` Eduardo Habkost
2014-11-07 16:04 ` [Qemu-devel] [PATCH 2/3] vl: sanity check cpu topology Andrew Jones
2014-11-11 12:41 ` Eduardo Habkost
2014-11-11 14:37 ` Andrew Jones
2014-11-11 15:48 ` Eduardo Habkost
2014-11-11 17:04 ` Andrew Jones
2014-11-11 17:27 ` Eduardo Habkost
2014-11-11 18:31 ` Eduardo Habkost
2014-11-12 9:14 ` Andrew Jones
2014-11-07 16:04 ` Andrew Jones [this message]
2014-11-11 11:15 ` [Qemu-devel] [PATCH 0/3] vl: smp_parse sanity checks Paolo Bonzini
2014-11-11 12:42 ` Eduardo Habkost
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=1415376280-14130-4-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).