From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: peter.maydell@linaro.org, mimu@linux.vnet.ibm.com, agraf@suse.de,
qemu-devel@nongnu.org, borntraeger@de.ibm.com,
bharata@linux.vnet.ibm.com, cornelia.huck@de.ibm.com,
"Andreas Färber" <afaerber@suse.de>,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH] cpu: Register QOM links at /machine/cpus/<index>
Date: Mon, 04 May 2015 11:59:52 +0200 [thread overview]
Message-ID: <55474318.8090501@redhat.com> (raw)
In-Reply-To: <20150504114728.0dd227dd@nial.brq.redhat.com>
On 04/05/2015 11:47, Igor Mammedov wrote:
> On Thu, 30 Apr 2015 16:19:07 -0300
> Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> > This will provide a predictable path for the CPU objects, and a more
> > powerful alternative for the query-cpus QMP command, as now every QOM
> > property on CPU objects can be easily queried.
>
> provided the way cpu_index is generated, path won't be predictable/stable
> with CPU unplug. I'd rather use DEVICE->id instead of cpu_index.
Can we use the APIC id then? Perhaps wrapped with a CPUState-level
method get_stable_processor_id()?
Paolo
next prev parent reply other threads:[~2015-05-04 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 19:19 [Qemu-devel] [PATCH] cpu: Register QOM links at /machine/cpus/<index> Eduardo Habkost
2015-05-01 1:51 ` Peter Crosthwaite
2015-05-01 12:17 ` Eduardo Habkost
2015-05-04 9:47 ` Igor Mammedov
2015-05-04 9:59 ` Paolo Bonzini [this message]
2015-05-04 13:16 ` Igor Mammedov
2015-05-04 13:19 ` Paolo Bonzini
2015-05-04 14:05 ` Eduardo Habkost
2015-05-04 15:53 ` Paolo Bonzini
2015-05-04 18:37 ` Eduardo Habkost
2015-05-04 13:37 ` Eduardo Habkost
-- strict thread matches above, loose matches on Subject: below --
2015-04-30 20:21 Andreas Färber
2015-04-30 21:47 ` Paolo Bonzini
2015-05-01 1:54 ` Peter Crosthwaite
2015-05-01 11:59 ` Eduardo Habkost
2015-05-05 10:23 ` Paolo Bonzini
2015-05-01 12:08 ` 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=55474318.8090501@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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.