From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
chrisw@sous-sol.org
Subject: Re: [PATCH 0/3] Expose thread id through info cpus
Date: Thu, 06 Mar 2008 08:55:15 +0200 [thread overview]
Message-ID: <47CF9553.3090600@qumranet.com> (raw)
In-Reply-To: <12047472711034-git-send-email-gcosta@redhat.com>
Glauber Costa wrote:
> Hey,
>
> This patch series expose the actual thread id of each cpu via the qemu
> monitor. It is done through "info cpus", which I though would be the
> most natural command to do it. (If you disagree, please voice it)
>
> Goal is to allow tools like libvirt to easily grab it and feed taskset
> for thinks like cpu pinning, etc
>
> AFAIK, qemu runs all cpus in the same process, so for plain qemu, all cpus
> will show the same id. But KVM can benefit from it, by overriding this data
> in its ap initialization
>
> Of the whole series, only the last patch is kvm-specific.
>
> Many thanks to Anthony, who pointed me that this approach was possible.
>
>
>
Applied all, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, glommer@gmail.com,
qemu-devel@nongnu.org, chrisw@sous-sol.org
Subject: [Qemu-devel] Re: [PATCH 0/3] Expose thread id through info cpus
Date: Thu, 06 Mar 2008 08:55:15 +0200 [thread overview]
Message-ID: <47CF9553.3090600@qumranet.com> (raw)
In-Reply-To: <12047472711034-git-send-email-gcosta@redhat.com>
Glauber Costa wrote:
> Hey,
>
> This patch series expose the actual thread id of each cpu via the qemu
> monitor. It is done through "info cpus", which I though would be the
> most natural command to do it. (If you disagree, please voice it)
>
> Goal is to allow tools like libvirt to easily grab it and feed taskset
> for thinks like cpu pinning, etc
>
> AFAIK, qemu runs all cpus in the same process, so for plain qemu, all cpus
> will show the same id. But KVM can benefit from it, by overriding this data
> in its ap initialization
>
> Of the whole series, only the last patch is kvm-specific.
>
> Many thanks to Anthony, who pointed me that this approach was possible.
>
>
>
Applied all, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-03-06 6:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:01 [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] use a thread id variable Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] augment info cpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] KVM: use actual thread id for vcpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-09 9:26 ` [Qemu-devel] [PATCH] use a thread id variable Gilad Ben-Yossef
2008-03-09 9:26 ` Gilad Ben-Yossef
2008-03-09 11:58 ` Jamie Lokier
2008-03-09 11:58 ` Jamie Lokier
2008-03-09 14:52 ` Gilad Ben-Yossef
2008-03-09 14:52 ` Gilad Ben-Yossef
2008-03-09 16:12 ` M. Warner Losh
2008-03-09 16:12 ` M. Warner Losh
2008-03-17 17:55 ` Glauber Costa
2008-03-17 17:55 ` Glauber Costa
2008-03-09 16:09 ` M. Warner Losh
2008-03-09 16:09 ` M. Warner Losh
2008-03-09 20:01 ` Jamie Lokier
2008-03-09 20:01 ` Jamie Lokier
2008-03-09 16:23 ` Daniel P. Berrange
2008-03-09 16:23 ` [kvm-devel] " Daniel P. Berrange
2008-03-05 20:07 ` [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-05 20:07 ` [Qemu-devel] " Glauber Costa
2008-03-06 6:55 ` Avi Kivity [this message]
2008-03-06 6:55 ` Avi Kivity
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=47CF9553.3090600@qumranet.com \
--to=avi@qumranet.com \
--cc=chrisw@sous-sol.org \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--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.