From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JWzuB-0002ds-AJ for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:07:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JWzu6-0002dF-4T for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:07:58 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JWzu5-0002d9-Rt for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:07:53 -0500 Received: from wf-out-1314.google.com ([209.85.200.175]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JWzu5-0000J9-Ie for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:07:53 -0500 Received: by wf-out-1314.google.com with SMTP id 28so2075237wff.4 for ; Wed, 05 Mar 2008 12:07:50 -0800 (PST) Message-ID: <5d6222a80803051207l251c1664i879d9c3543805f13@mail.gmail.com> Date: Wed, 5 Mar 2008 17:07:50 -0300 From: "Glauber Costa" In-Reply-To: <12047472711034-git-send-email-gcosta@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <12047472711034-git-send-email-gcosta@redhat.com> Subject: [Qemu-devel] Re: [PATCH 0/3] Expose thread id through info cpus Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Glauber Costa Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org, chrisw@sous-sol.org Oops! Forgot the -n option in git. Anyway, the series is small and straightforward, so I'm not reposting it. If there is any doubt about the ordering, please tell me. On Wed, Mar 5, 2008 at 5:01 PM, 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. > > > -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act."