From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] provide cpu_index to env mapping
Date: Tue, 09 Jun 2009 19:42:42 +0300 [thread overview]
Message-ID: <4A2E9102.6000100@redhat.com> (raw)
In-Reply-To: <20090609164009.GP11966@poweredge.glommer>
Glauber Costa wrote:
> On Tue, Jun 09, 2009 at 07:25:02PM +0300, Avi Kivity wrote:
>
>> Glauber Costa wrote:
>>
>>> There are some people interested in, given a cpu number,
>>> pick its CPUState. KVM is an example, although not yet in tree.
>>> This patch provides a way of doing that.
>>>
>>>
>>>
>> I think it's better to migrate kvm towards using env as the handle
>> instead of the cpu index.
>>
> btw: the particular user of this is cpu hotplug.
>
Well, cpu hotplug should definitely use the apic id.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-09 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 16:15 [Qemu-devel] [PATCH] provide cpu_index to env mapping Glauber Costa
2009-06-09 16:25 ` Avi Kivity
2009-06-09 16:40 ` Glauber Costa
2009-06-09 16:42 ` Avi Kivity [this message]
2009-06-09 16:52 ` Glauber Costa
2009-06-09 16:46 ` Gleb Natapov
2009-06-09 16:45 ` Gleb Natapov
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=4A2E9102.6000100@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@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).