On Wed, 18 Oct 2017 14:33:49 +0200 Paolo Bonzini <pbonz...@redhat.com> wrote:
> On 18/10/2017 14:27, Daniel P. Berrange wrote: > >>> -object numa-node,id=numa0 > >>> -object numa-node,id=numa1 > >>> -object cpu,id=cpu0,node=numa0,socket=0,core=0,thread=0 > >>> -object cpu,id=cpu1,node=numa0,socket=0,core=1,thread=0 > >>> -object cpu,id=cpu2,node=numa0,socket=1,core=0,thread=0 > >>> -object cpu,id=cpu3,node=numa0,socket=1,core=1,thread=0 > >>> -object cpu,id=cpu4,node=numa1,socket=2,core=0,thread=0 > >>> -object cpu,id=cpu5,node=numa1,socket=2,core=1,thread=0 > >>> -object cpu,id=cpu6,node=numa1,socket=3,core=0,thread=0 > >>> -object cpu,id=cpu7,node=numa1,socket=3,core=1,thread=0 > >>> > >>> (perhaps -device instead of -object above, but that's a minor detail) > >> I understand that this is just an example, but wasn't this what is solved > >> by > >> > >> -smp 8,sockets=4,cores=2,thread=1 > >> -numa node,nodeid=0 -numa cpu,node-id=0,socket-id=0-1 > >> -numa node,nodeid=1 -numa cpu,node-id=0,socket-id=2-3 > > IIUC, that lets you associate CPUs with NUMA nodes without having to know > > the internal QEMU indexes. It won't help you with any monitor commands you > > need to run later that expect the CPU index as input value. My example > > where lets you assign IDs to each CPU, which can then be used for montor > > commands too - i should have illustrated that bit of it too. > > I guess query-hotpluggable-cpus could also grow a first-cpu-index in the > returned data. I guess query-cpus can/does provide cpu-index already, for query-hotpluggable-cpus it would depend in what's shown there (would work fro x86/arm/s390 as they publish there CPUState based objects, but spapr puts cores there which themselves do not have cpu-index, their children do though) > > Paolo >
