From: Eduardo Habkost <ehabkost@redhat.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: Alexandre DERUMIER <aderumier@odiso.com>,
qemu-devel <qemu-devel@nongnu.org>,
drjones@redhat.com, Markus Armbruster <armbru@redhat.com>,
bharata@linux.vnet.ibm.com, Fam Zheng <famz@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v7] docs: add cpu-hotplug.txt
Date: Fri, 9 Sep 2016 16:20:18 -0300 [thread overview]
Message-ID: <20160909192018.GK24695@thinpad.lan.raisama.net> (raw)
In-Reply-To: <90ccb629-15b4-784c-f14b-cdfda6f08047@cn.fujitsu.com>
On Wed, Sep 07, 2016 at 09:52:59AM +0800, Dou Liyang wrote:
[...]
> >
> > The option:
> > -smp MODEL,+FOO,+BAR
>
> I guess you may mean "-cpu", not "-smp"
Oops, yes. Thanks. :)
>
> > is internally translated to:
> > -global MODEL.FOO=on
> > -global MODEL.BAR=on
> > in addition to setting the CPU model for creating initial CPUs to
> > MODEL.
> >
>
> I see.
>
[...]
> > > >
> > > > -smp sockets=2,cores=2,maxcpus=4
> > >
> > > > -device qemu64-x86_64-cpu,id=cpu1,socket-id=1,core-id=1,thread-id=0
> > > > -device qemu64-x86_64-cpu,id=cpu1,socket-id=1,core-id=2,thread-id=0
> > > > -device qemu64-x86_64-cpu,id=cpu3,socket-id=2,core-id=1,thread-id=0
> > > > -device qemu64-x86_64-cpu,id=cpu4,socket-id=2,core-id=2,thread-id=0
> > > >
> > > > or does I need minimum 1 non unplugable cpu
> >
> > As mentioned above, the default number of CPUs is 1, so "-smp
> > sockets=2" is the same as "-smp 1,sockets=2".
> >
> > I assume you mean something like "-smp 0", but that doesn't work
> > today. I would like to eventually allow all CPUs to be created
> > using -device, but that's not possible yet.
>
> I am interested in what is the benefit, if we can create all CPUs using
> -device. :)
Do you mean the benefit of not allowing "-smp 0", or the benefit
of using -device?
The benefit of not allowing "-smp 0" is none, except that we
probably have existing code that would break if we allow that,
and that code needs to be fixed first.
About -device: the benefit is having an uniform interface to
create every kind of device, and using the same interface and
options for hotplugged CPUs and non-hotplug CPUs.
(But one problem with -device today is that management software
needs to know what are the valid socket/core/thread arguments for
the machine but can't run a 'query-hotpluggable-cpus' command
before launching QEMU [unless it launches QEMU twice]).
--
Eduardo
prev parent reply other threads:[~2016-09-09 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 1:50 [Qemu-devel] [PATCH v7] docs: add cpu-hotplug.txt Dou Liyang
2016-08-22 8:56 ` Alexandre DERUMIER
2016-08-23 5:17 ` Dou Liyang
2016-09-06 20:05 ` Eduardo Habkost
2016-09-07 1:52 ` Dou Liyang
2016-09-09 19:20 ` Eduardo Habkost [this message]
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=20160909192018.GK24695@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=aderumier@odiso.com \
--cc=armbru@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=douly.fnst@cn.fujitsu.com \
--cc=drjones@redhat.com \
--cc=famz@redhat.com \
--cc=imammedo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.