From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add another sanity check to smp_parse() function
Date: Tue, 18 Aug 2015 16:39:10 -0700 [thread overview]
Message-ID: <55D3C21E.4020401@redhat.com> (raw)
In-Reply-To: <1437573590-2801-1-git-send-email-thuth@redhat.com>
On 22/07/15 06:59, Thomas Huth wrote:
> The code in smp_parse already checks the topology information for
> sockets * cores * threads < cpus and bails out with an error in
> that case. However, it is still possible to supply a bad configuration
> the other way round, e.g. with:
>
> qemu-system-xxx -smp 4,sockets=1,cores=4,threads=2
>
> QEMU then still starts the guest, with topology configuration that
> is rather incomprehensible and likely not what the user wanted.
> So let's add another check to refuse such wrong configurations.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> vl.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/vl.c b/vl.c
> index 5856396..c8d24b1 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1224,7 +1224,13 @@ static void smp_parse(QemuOpts *opts)
> exit(1);
> }
>
> - max_cpus = qemu_opt_get_number(opts, "maxcpus", 0);
> + max_cpus = qemu_opt_get_number(opts, "maxcpus", cpus);
> + if (sockets * cores * threads > max_cpus) {
> + fprintf(stderr, "cpu topology: error: "
> + "sockets (%u) * cores (%u) * threads (%u) > maxcpus (%u)\n",
> + sockets, cores, threads, max_cpus);
> + exit(1);
> + }
>
> smp_cpus = cpus;
> smp_cores = cores > 0 ? cores : 1;
*ping*
Thomas
next prev parent reply other threads:[~2015-08-18 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:59 [Qemu-devel] [PATCH] Add another sanity check to smp_parse() function Thomas Huth
2015-07-23 12:07 ` Igor Mammedov
2015-07-24 11:53 ` Thomas Huth
2015-08-18 23:39 ` Thomas Huth [this message]
2015-08-19 15:58 ` Eduardo Habkost
2015-08-25 13:25 ` Thomas Huth
2015-08-26 11:36 ` Cornelia Huck
2015-08-26 12:11 ` Bastian Koppelmann
2015-08-26 16:02 ` 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=55D3C21E.4020401@redhat.com \
--to=thuth@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).