From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JWzqJ-0001UF-M4 for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:03:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JWzqJ-0001U3-2T for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:03:59 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JWzqI-0001U0-Sx for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:03:58 -0500 Received: from mx1.redhat.com ([66.187.233.31]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JWzqI-0006w7-IH for qemu-devel@nongnu.org; Wed, 05 Mar 2008 15:03:58 -0500 From: Glauber Costa Date: Wed, 5 Mar 2008 17:01:08 -0300 Message-Id: <12047472711034-git-send-email-gcosta@redhat.com> Subject: [Qemu-devel] [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: kvm-devel@lists.sourceforge.net Cc: glommer@gmail.com, qemu-devel@nongnu.org, chrisw@sous-sol.org 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.