From: Igor Mammedov <imammedo@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, ehabkost@redhat.com,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] docs: Document vCPU hotplug procedure
Date: Mon, 1 Oct 2018 10:59:04 +0200 [thread overview]
Message-ID: <20181001105904.4c155ffd@redhat.com> (raw)
In-Reply-To: <20181001081845.GD25720@paraplu>
On Mon, 1 Oct 2018 10:18:45 +0200
Kashyap Chamarthy <kchamart@redhat.com> wrote:
> On Thu, Sep 27, 2018 at 04:33:16PM +0200, Markus Armbruster wrote:
> > Igor Mammedov <imammedo@redhat.com> writes:
> >
> > > On Tue, 25 Sep 2018 18:02:48 +0200
> > > Kashyap Chamarthy <kchamart@redhat.com> wrote:
>
> [...]
>
> > >> +(3) Check which socket is free to allow hotplugging a CPU::
> > > may be: which cpus are possible to plug (an entry with qom-path
> > > property describes an existing cpu)
> >
> > Suggest
> >
> > (3) Find out which CPU types could be plugged, and into which sockets:
>
> Yeah, clearer.
>
> [...]
>
> > >> +(4) We can see that socket 1 is free,
> >
> > How? I know, but only because I just read the documentation of
> > query-hotpluggable-cpus. Which by the way sucks. For instance, will
> > the command always return exactly one HotpluggableCPU object per socket?
>
> About the 'how', I was not entirely sure, hence my request in the cover
> letter.
>
> > Anyway, what about this:
> >
> > The command returns an object with a "qom-path" member for each
> > present CPU. In this case, it shows an IvyBridge-IBRS-x86_64-cpu in
> > socket 0.
> >
> > It returns an object without a "qom-path" for every possibly CPU
> > hot-plug. In this case, it shows you can plug an
> > IvyBridge-IBRS-x86_64-cpu into socket 1, and the additional
> > properties you need to pass to device_add for that.
not really sure my English (CCed Eric) but to match 'an object' with
the rest of sentence:
It returns an object without a "qom-path" for a possible to hot-plug CPU.
+
In this case, it shows you can plug an IvyBridge-IBRS-x86_64-cpu
into socket 1/core = 0/thread 0, where 'props' list describes
additional properties you need to pass to device_add for hot-pluging
that CPU.
>
> Crystal clear.
>
> Many thanks for the review!
>
> > > ... and 'arguments' provide a list of property/value pairs to create
> > > corresponding cpu.
> > >
> > >> + "IvyBridge-IBRS-x86_64-cpu"::
> >
> > Suggest
> >
> > (4) Hot-plug an additional CPU:
>
> [...]
>
next prev parent reply other threads:[~2018-10-01 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180925160248.30801-1-kchamart@redhat.com>
[not found] ` <20180925160248.30801-3-kchamart@redhat.com>
[not found] ` <20180926172427.05a2de94@redhat.com>
[not found] ` <87zhw33t8z.fsf@dusky.pond.sub.org>
2018-10-01 8:18 ` [Qemu-devel] [PATCH v2 2/2] docs: Document vCPU hotplug procedure Kashyap Chamarthy
2018-10-01 8:59 ` Igor Mammedov [this message]
2018-10-08 19:10 ` Eric Blake
2018-10-09 9:59 ` Igor Mammedov
[not found] ` <20180925160248.30801-2-kchamart@redhat.com>
2018-10-01 9:28 ` [Qemu-devel] [PATCH v2 1/2] Deprecate QMP `cpu-add` Thomas Huth
2018-10-01 12:40 ` Kashyap Chamarthy
2018-10-08 13:29 ` Markus Armbruster
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=20181001105904.4c155ffd@redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kchamart@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).