From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41390)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1VdQ3O-00005B-Ra
	for qemu-devel@nongnu.org; Mon, 04 Nov 2013 14:43:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <B07421@freescale.com>) id 1VdQ3H-0006cj-G2
	for qemu-devel@nongnu.org; Mon, 04 Nov 2013 14:43:14 -0500
Message-ID: <1383594148.25829.6.camel@snotra.buserror.net>
From: Scott Wood <scottwood@freescale.com>
Date: Mon, 4 Nov 2013 13:42:28 -0600
In-Reply-To: <50BDF498-54CD-45C6-AB84-F7F1252FD8F6@suse.de>
References: <1383527453-6489-1-git-send-email-aik@ozlabs.ru>
	<50BDF498-54CD-45C6-AB84-F7F1252FD8F6@suse.de>
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>, QEMU Developers <qemu-devel@nongnu.org>, Bharat Bhushan <bharat.bhushan@freescale.com>, Paolo Bonzini <pbonzini@redhat.com>, Paul Mackerras <paulus@samba.org>, Badari Pulavarty <pbadari@linux.vnet.ibm.com>, "list@suse.de:PReP" <qemu-ppc@nongnu.org>, David Gibson <david@gibson.dropbear.id.au>

On Mon, 2013-11-04 at 10:41 +0100, Alexander Graf wrote:
> What we really have are 3 semantically separate entities:
> 
>   * QEMU internal cpu id
>   * KVM internal cpu id
>   * DT exposed cpu id
> 
> As you have noted, it's a good idea to keep the QEMU internal cpu id
> linear, thus completely separate from the others. The DT exposed cpu id
> should be 100% local to hw/ppc/spapr*.c. I don't think any code outside
> of the DT generation and anything that accesses the "Virtual Processor
> Number" in sPAPR needs to care about the DT cpu id. All that code is
> 100% KVM agnostic.

This patch isn't just for sPAPR...  On e500 the DT cpu id is supposed to
match the MPIC cpu id.

-Scott