From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/3] Expose thread id through info cpus Date: Thu, 06 Mar 2008 08:55:15 +0200 Message-ID: <47CF9553.3090600@qumranet.com> References: <12047472711034-git-send-email-gcosta@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org, chrisw@sous-sol.org To: Glauber Costa Return-path: In-Reply-To: <12047472711034-git-send-email-gcosta@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org 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/ From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JXA3q-00008P-O4 for qemu-devel@nongnu.org; Thu, 06 Mar 2008 01:58:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JXA3o-00007X-OH for qemu-devel@nongnu.org; Thu, 06 Mar 2008 01:58:37 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JXA3o-00007R-HS for qemu-devel@nongnu.org; Thu, 06 Mar 2008 01:58:36 -0500 Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194] helo=il.qumranet.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JXA3n-0007S3-Q1 for qemu-devel@nongnu.org; Thu, 06 Mar 2008 01:58:36 -0500 Message-ID: <47CF9553.3090600@qumranet.com> Date: Thu, 06 Mar 2008 08:55:15 +0200 From: Avi Kivity MIME-Version: 1.0 References: <12047472711034-git-send-email-gcosta@redhat.com> In-Reply-To: <12047472711034-git-send-email-gcosta@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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, glommer@gmail.com, qemu-devel@nongnu.org, chrisw@sous-sol.org 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.