From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: KVM CPU Numbering
Date: Sun, 03 Oct 2010 10:45:55 +0200
Message-ID: <4CA842C3.5030401@redhat.com>
References: <AANLkTinP1uY_bdLpZZ_ziJdpG3Ku+koGukMZ0V1xkhWL@mail.gmail.com> <AANLkTi=WU9MLDc_WX4YGiSKTBBus+PMU7+bOWuGv+Rup@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Yushu Yao <yao.yushu@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:6113 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752512Ab0JCIqA (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 3 Oct 2010 04:46:00 -0400
In-Reply-To: <AANLkTi=WU9MLDc_WX4YGiSKTBBus+PMU7+bOWuGv+Rup@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  On 10/01/2010 01:23 PM, Yushu Yao wrote:
> Hi Experts,
>
>   Question:
>
> IN Qemu Monitor if i type "info cpus" the shown cpu list like:
>
> QEMU 0.12.5 monitor - type 'help' for more information
> (qemu) info cpus
> * CPU #0: pc=0x00000000fffffff0 thread_id=11170
>    CPU #1: pc=0x00000000fffffff0 (halted) thread_id=11171
>    CPU #2: pc=0x00000000fffffff0 (halted) thread_id=11172
>    CPU #3: pc=0x00000000fffffff0 (halted) thread_id=11173
>    CPU #4: pc=0x00000000fffffff0 (halted) thread_id=11174
>    CPU #5: pc=0x00000000fffffff0 (halted) thread_id=11175
>    CPU #6: pc=0x00000000fffffff0 (halted) thread_id=11176
>    CPU #7: pc=0x00000000fffffff0 (halted) thread_id=11177
>
> Does these #0, #1, ... map to the numbering in /proc/cpuinfo of the
> guest? (processor : xxx)

The map to the guest's APIC ID of those processors (also visible in 
/proc/cpuinfo, under the 'initial apicid' field).


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.