Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-05 Thread Scott Wood
On Tue, 2013-11-05 at 07:00 +0100, Alexander Graf wrote: > > Am 05.11.2013 um 02:48 schrieb Scott Wood : > > > On Tue, 2013-11-05 at 12:26 +1100, Alexey Kardashevskiy wrote: > >> On 11/05/2013 06:42 AM, Scott Wood wrote: > >>> On Mon, 2013-11-04 at 10:41 +0100, Alexander Graf wrote: > What w

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Alexander Graf
Am 05.11.2013 um 02:48 schrieb Scott Wood : > On Tue, 2013-11-05 at 12:26 +1100, Alexey Kardashevskiy wrote: >> 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

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Scott Wood
On Tue, 2013-11-05 at 12:26 +1100, Alexey Kardashevskiy wrote: > 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 > >>

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Alexey Kardashevskiy
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

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Scott Wood
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 se

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Alexander Graf
On 04.11.2013, at 10:58, Alexey Kardashevskiy wrote: > On 11/04/2013 08:41 PM, Alexander Graf wrote: >> >> On 04.11.2013, at 02:10, Alexey Kardashevskiy wrote: >> >>> Normally CPUState::cpu_index is used to pick the right CPU for various >>> operations. However default consecutive numbering d

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Alexey Kardashevskiy
On 11/04/2013 08:41 PM, Alexander Graf wrote: > > On 04.11.2013, at 02:10, Alexey Kardashevskiy wrote: > >> Normally CPUState::cpu_index is used to pick the right CPU for various >> operations. However default consecutive numbering does not always work >> for POWERPC. >> >> For example, on POWER

Re: [Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-04 Thread Alexander Graf
On 04.11.2013, at 02:10, Alexey Kardashevskiy wrote: > Normally CPUState::cpu_index is used to pick the right CPU for various > operations. However default consecutive numbering does not always work > for POWERPC. > > For example, on POWER7 (which supports 4 threads per core), > "-smp 8,threads

[Qemu-devel] [PATCH v3] ppc: introduce CPUPPCState::cpu_dt_id

2013-11-03 Thread Alexey Kardashevskiy
Normally CPUState::cpu_index is used to pick the right CPU for various operations. However default consecutive numbering does not always work for POWERPC. For example, on POWER7 (which supports 4 threads per core), "-smp 8,threads=4" should create CPUs with indexes 0,1,2,3,4,5,6,7 and "-smp 8,thre