From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Scott Wood <scottwood@freescale.com>, Alexander Graf <agraf@suse.de>
Cc: 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>
Subject: Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id
Date: Tue, 05 Nov 2013 12:26:37 +1100 [thread overview]
Message-ID: <5278494D.7050809@ozlabs.ru> (raw)
In-Reply-To: <1383594148.25829.6.camel@snotra.buserror.net>
On 11/05/2013 06:42 AM, Scott Wood wrote:
> 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.
At least is my patch correct for e500? I do not really know what is the
difference between e500 and spapr in this part.
--
Alexey
next prev parent reply other threads:[~2013-11-05 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 1:10 [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id Alexey Kardashevskiy
2013-11-04 9:41 ` Alexander Graf
2013-11-04 9:58 ` Alexey Kardashevskiy
2013-11-04 10:13 ` Alexander Graf
2013-11-04 19:42 ` Scott Wood
2013-11-05 1:26 ` Alexey Kardashevskiy [this message]
2013-11-05 1:48 ` Scott Wood
2013-11-05 6:00 ` Alexander Graf
2013-11-06 1:04 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5278494D.7050809@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=bharat.bhushan@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--cc=pbadari@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.