qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vl: rework smp_parse
Date: Fri, 7 Nov 2014 10:29:36 +0100	[thread overview]
Message-ID: <20141107092935.GB3004@hawk.usersys.redhat.com> (raw)
In-Reply-To: <545BF212.2090404@redhat.com>

On Thu, Nov 06, 2014 at 11:11:30PM +0100, Paolo Bonzini wrote:
> 
> 
> On 06/11/2014 17:09, Andrew Jones wrote:
> > +        if (sockets * cores * threads != max_cpus) {
> > +            fprintf(stderr, "cpu topology: "
> > +                    "sockets (%u) * cores (%u) * threads (%u) != max_cpus (%u)\n",
> > +                    sockets, cores, threads, max_cpus);
> > +            exit(1);
> > +        }
> 
> I think this would cause too many failures in the wild.  Perhaps error
> out if it is lower, and warn if sockets * cores * threads > max_cpus
> since we actually allow hot-plug a thread at a time?

We'd still have more failures if we choose to error out when it's lower,
since we currently silently adjust threads in some of those cases, or
just don't care that the topology doesn't support up to maxcpus in other.

I'm not sure how best to go about modifying the command line semantics
in a backwards compatible way, other than to just create a new "-smp"
option. I'm open to all opinions and suggestions.

Thanks,
drew

  reply	other threads:[~2014-11-07  9:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 16:09 [Qemu-devel] [PATCH] vl: rework smp_parse Andrew Jones
2014-11-06 19:17 ` Eduardo Habkost
2014-11-07  9:22   ` Andrew Jones
2014-11-07 11:29     ` Andrew Jones
2014-11-06 22:11 ` Paolo Bonzini
2014-11-07  9:29   ` Andrew Jones [this message]
2014-11-07  9:40     ` Paolo Bonzini
2014-11-07  9:52       ` Andrew Jones
2014-11-07 11:21         ` Andrew Jones
2014-11-07 12:16           ` Eduardo Habkost
2014-11-07 12:23             ` Andrew Jones
2014-11-07 12:32               ` Eduardo Habkost
2014-11-07 16:03 ` Andrew Jones

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=20141107092935.GB3004@hawk.usersys.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).