On 02/19/2014 12:54 AM, Hu Tao wrote:
From: Paolo Bonzini pbonz...@redhat.com
This option provides the infrastructure for binding guest NUMA nodes
to host NUMA nodes. For example:
-object memory-ram,size=1024M,policy=membind,host-nodes=0,id=ram-node0 \
-numa
On Mon, Mar 03, 2014 at 05:10:20PM -0700, Eric Blake wrote:
On 02/19/2014 12:54 AM, Hu Tao wrote:
From: Paolo Bonzini pbonz...@redhat.com
This option provides the infrastructure for binding guest NUMA nodes
to host NUMA nodes. For example:
-object
From: Paolo Bonzini pbonz...@redhat.com
This option provides the infrastructure for binding guest NUMA nodes
to host NUMA nodes. For example:
-object memory-ram,size=1024M,policy=membind,host-nodes=0,id=ram-node0 \
-numa node,nodeid=0,cpus=0,memdev=ram-node0 \
-object
On Wed, 19 Feb 2014 15:54:01 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
From: Paolo Bonzini pbonz...@redhat.com
This option provides the infrastructure for binding guest NUMA nodes
to host NUMA nodes. For example:
-object memory-ram,size=1024M,policy=membind,host-nodes=0,id=ram-node0 \
Il 19/02/2014 10:50, Igor Mammedov ha scritto:
+numa_info[nodenr].node_mem = object_property_get_int(o, size,
NULL);
+numa_info[nodenr].node_memdev = MEMORY_BACKEND(o);
if you make numa_info QOM object node_memdev link property,
then above hunk could be replaced with just
