: HVM NUMA guest: pass NUMA information to libxc
PATCH 2/5 : HVM NUMA guest: pass NUMA information to libxc
This patch adds a "struct numa_guest_info" to libxc, which allows to specify a guest's NUMA topology along with the appropriate host binding.
Here the information will be filled out by the Python wrapper (I left out the libxl part for now), it will fill up the struct with sensible default values (equal distribution), only the number of guest nodes should be specified by the caller. The information is passed on to the hvm_info_table. The respective memory allocation is in another patch.
Regards,
Andre.
Signature · 9 lines
Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 488-3567-12 ----to satisfy European Law for business letters: Advanced Micro Devices GmbH Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632
commit b4ee75af6f6220bdafccf75c9bc6e4915a413b18
Author: Andre Przywara <[email protected]> Date: Mon Feb 1 12:36:28 2010 +0100
add struct numainfo to interface and parse xend passed NUMA info and pass on to libxc
tools/libxc/xc_hvm_build.c +12 -4
@@ -106,6 +106,7 @@ static int loadelfimage(static int setup_guest (int xc_handle,uint32_t dom,int memsize,int target, +struct numa_guest_info *numainfo,char *image,unsigned long image_size) {xen_pfn_t *page_array =NULL ;
@@ -334,6 +335,7 @@ static int xc_hvm_build_internal(int xc_handle,uint32_t domid, int memsize, int target, + struct numa_guest_info *numainfo, char *image, unsigned long image_size) {
@@ -343,7 +345,8 @@ static int xc_hvm_build_internal(int xc_handle,return -1 ; } -return setup_guest (xc_handle, domid, memsize, target, image, image_size); +return setup_guest (xc_handle, domid, memsize, target, + numainfo, image, image_size); }/* xc_hvm_build:
@@ -352,6 +355,7 @@ static int xc_hvm_build_internal(int xc_handle,int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_name) {char *image;
@@ -362,7 +366,8 @@ int xc_hvm_build(int xc_handle, ((image = xc_read_image(image_name, &image_size)) == NULL) )return -1 ; - sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, image, image_size); + sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, + numainfo, image, image_size);free (image);
@@ -379,6 +384,7 @@ int xc_hvm_build_target_mem(int xc_handle,uint32_t domid, int memsize, int target, + struct numa_guest_info *numainfo, const char *image_name) { char *image;
@@ -389,7 +395,8 @@ int xc_hvm_build_target_mem(int xc_handle, ((image = xc_read_image(image_name, &image_size)) == NULL) )return -1 ; - sts =xc_hvm_build_internal (xc_handle, domid, memsize, target, image, image_size); + sts =xc_hvm_build_internal (xc_handle, domid, memsize, target, + numainfo, image, image_size);free (image);
@@ -402,6 +409,7 @@ int xc_hvm_build_target_mem(int xc_handle,int xc_hvm_build_mem (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_buffer,unsigned long image_size) {
@@ -425,7 +433,7 @@ int xc_hvm_build_mem(int xc_handle, } sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, - img, img_len); + numainfo, img, img_len);/* xc_inflate_buffer may return the original buffer pointer (for for already inflated buffers), so exercise some care in freeing */
tools/libxc/xenguest.h +10 -0
@@ -62,6 +62,13 @@ int xc_domain_restore(int xc_handle, int io_fd, uint32_t dom, unsigned int console_evtchn, unsigned long *console_mfn, unsigned int hvm, unsigned int pae, int superpages); +struct numa_guest_info { +int num_nodes; +int *guest_to_host_node; +int *vcpu_to_node; +uint64_t *node_mem; +}; +/** * This function will create a domain for a paravirtualized Linux * using file names pointing to kernel and ramdisk
@@ -143,17 +150,20 @@ int xc_linux_build_mem(int xc_handle,int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numa_info,const char *image_name);int xc_hvm_build_target_mem (int xc_handle,uint32_t domid,int memsize,int target, +struct numa_guest_info *numa_info,const char *image_name);int xc_hvm_build_mem (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numa_info,const char *image_buffer,unsigned long image_size);
tools/libxc/xg_private.c +1 -0
@@ -177,6 +177,7 @@ __attribute__((weak))int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_name) { errno =ENOSYS ;
tools/libxl/libxl_dom.c +1 -1
@@ -168,7 +168,7 @@ int build_hvm(struct libxl_ctx *ctx, uint32_t domid, {int ret; - ret =xc_hvm_build_target_mem (ctx->xch, domid, (info->max_memkb - info->video_memkb) /1024 , (info->target_memkb - info->video_memkb) /1024 , info->kernel); + ret =xc_hvm_build_target_mem (ctx->xch, domid, (info->max_memkb - info->video_memkb) /1024 , (info->target_memkb - info->video_memkb) /1024 ,NULL , info->kernel);if (ret) {XL_LOG_ERRNOVAL (ctx,XL_LOG_ERROR , ret,"hvm building failed" );return ERROR_FAIL ;
tools/python/xen/lowlevel/xc/xc.c +63 -8
99 lines not on this page · raw message
tools/python/xen/xend/image.py +2 -1
@@ -961,7 +961,8 @@ class HVMImageHandler(ImageHandler): vcpus = self.vm.getVCpuCount(), vcpu_avail = self.vm.getVCpuAvail(), acpi = self.acpi, - apic = self.apic) + apic = self.apic, + nodes = 0) rc['notes'] = { 'SUSPEND_CANCEL': 1 } rc['store_mfn'] = xc.hvm_get_param(self.vm.getDomid(),
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 215 lines · Andre Przywara
This patch adds a "struct
numa_guest_info" to libxc, which allows to specify a guest's NUMA topology along with the appropriate host binding. Here the information will be filled out by the Python wrapper (I left out the libxl part for now), it will fill up the struct with sensible default values (equal distribution), only the number of guest nodes should be specified by the caller. The information is passed on to thehvm_info_table. The respective memory allocation is in another patch.Signed-off-by Andre Przywara <[email protected]>Regards,
Andre.Signature · 16 lines
Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 488-3567-12 ----to satisfy European Law for business letters: Advanced Micro Devices GmbH Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 commit b4ee75af6f6220bdafccf75c9bc6e4915a413b18 Author: Andre Przywara <[email protected]> Date: Mon Feb 1 12:36:28 2010 +0100 add struct numainfo to interface and parse xend passed NUMA info and pass on to libxctools/libxc/xc_hvm_build.c +12
-4@@ -106,6 +106,7 @@ static int loadelfimage(static int setup_guest (int xc_handle,uint32_t dom,int memsize,int target, +struct numa_guest_info *numainfo,char *image,unsigned long image_size) {xen_pfn_t *page_array =NULL ;@@ -334,6 +335,7 @@ static int xc_hvm_build_internal(int xc_handle,uint32_t domid, int memsize, int target, + struct numa_guest_info *numainfo, char *image, unsigned long image_size) {@@ -343,7 +345,8 @@ static int xc_hvm_build_internal(int xc_handle,return -1 ; } -return setup_guest (xc_handle, domid, memsize, target, image, image_size); +return setup_guest (xc_handle, domid, memsize, target, + numainfo, image, image_size); }/* xc_hvm_build: @@ -352,6 +355,7 @@ static int xc_hvm_build_internal(int xc_handle,int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_name) {char *image;@@ -362,7 +366,8 @@ int xc_hvm_build(int xc_handle, ((image = xc_read_image(image_name, &image_size)) == NULL) )return -1 ; - sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, image, image_size); + sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, + numainfo, image, image_size);free (image);@@ -379,6 +384,7 @@ int xc_hvm_build_target_mem(int xc_handle,uint32_t domid, int memsize, int target, + struct numa_guest_info *numainfo, const char *image_name) { char *image;@@ -389,7 +395,8 @@ int xc_hvm_build_target_mem(int xc_handle, ((image = xc_read_image(image_name, &image_size)) == NULL) )return -1 ; - sts =xc_hvm_build_internal (xc_handle, domid, memsize, target, image, image_size); + sts =xc_hvm_build_internal (xc_handle, domid, memsize, target, + numainfo, image, image_size);free (image);@@ -402,6 +409,7 @@ int xc_hvm_build_target_mem(int xc_handle,int xc_hvm_build_mem (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_buffer,unsigned long image_size) {@@ -425,7 +433,7 @@ int xc_hvm_build_mem(int xc_handle, } sts =xc_hvm_build_internal (xc_handle, domid, memsize, memsize, - img, img_len); + numainfo, img, img_len);/* xc_inflate_buffer may return the original buffer pointer (for for already inflated buffers), so exercise some care in freeing */ tools/libxc/xenguest.h +10
-0@@ -62,6 +62,13 @@ int xc_domain_restore(int xc_handle, int io_fd, uint32_t dom, unsigned int console_evtchn, unsigned long *console_mfn, unsigned int hvm, unsigned int pae, int superpages); +struct numa_guest_info { +int num_nodes; +int *guest_to_host_node; +int *vcpu_to_node; +uint64_t *node_mem; +}; +/** * This function will create a domain for a paravirtualized Linux * using file names pointing to kernel and ramdisk @@ -143,17 +150,20 @@ int xc_linux_build_mem(int xc_handle,int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numa_info,const char *image_name);int xc_hvm_build_target_mem (int xc_handle,uint32_t domid,int memsize,int target, +struct numa_guest_info *numa_info,const char *image_name);int xc_hvm_build_mem (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numa_info,const char *image_buffer,unsigned long image_size);tools/libxc/xg_private.c +1
-0@@ -177,6 +177,7 @@ __attribute__((weak))int xc_hvm_build (int xc_handle,uint32_t domid,int memsize, +struct numa_guest_info *numainfo,const char *image_name) { errno =ENOSYS ;tools/libxl/libxl_dom.c +1
-1@@ -168,7 +168,7 @@ int build_hvm(struct libxl_ctx *ctx, uint32_t domid, {int ret; - ret =xc_hvm_build_target_mem (ctx->xch, domid, (info->max_memkb - info->video_memkb) /1024 , (info->target_memkb - info->video_memkb) /1024 , info->kernel); + ret =xc_hvm_build_target_mem (ctx->xch, domid, (info->max_memkb - info->video_memkb) /1024 , (info->target_memkb - info->video_memkb) /1024 ,NULL , info->kernel);if (ret) {XL_LOG_ERRNOVAL (ctx,XL_LOG_ERROR , ret,"hvm building failed" );return ERROR_FAIL ;tools/python/xen/lowlevel/xc/xc.c +11
-7@@ -915,15 +915,19 @@ static PyObject *pyxc_hvm_build(XcObject *self,int i;char *image;int memsize, target=-1 , vcpus =1 , acpi =0 , apic =1 ; +int numanodes; +struct numa_guest_info numainfo;PyObject *vcpu_avail_handle =NULL ; +PyObject *nodemem_handle =NULL ;uint8_t vcpu_avail[HVM_MAX_VCPUS /8 ]; -static char *kwd_list[] = {"domid" , -"memsize" ,"image" ,"target" ,"vcpus" , -"vcpu_avail" ,"acpi" ,"apic" ,NULL }; -if ( !PyArg_ParseTupleAndKeywords (args, kwds,"iis|iiOii" , kwd_list, +static char *kwd_list[] = {"domid" ,"memsize" ,"image" ,"target" , +"vcpus" ,"vcpu_avail" ,"acpi" ,"apic" , +"nodes" ,"nodemem" ,NULL }; +if ( !PyArg_ParseTupleAndKeywords (args, kwds,"iis|iiOiiiO" , kwd_list, &dom, &memsize, &image, &target, &vcpus, - &vcpu_avail_handle, &acpi, &apic) ) + &vcpu_avail_handle, &acpi, &apic, + &numanodes, &nodemem_handle) )return NULL ;memset (vcpu_avail,0 ,sizeof (vcpu_avail));@@ -954,8 +958,50 @@ static PyObject *pyxc_hvm_build(XcObject *self,if ( target ==-1 ) target = memsize; -if (xc_hvm_build_target_mem (self->xc_handle, dom, memsize, - target, image) !=0 ) + numainfo.num_nodes = numanodes; + numainfo.guest_to_host_node =malloc (numanodes *sizeof (int ));
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 972
Quoted 10 lines
tools/python/xen/lowlevel/xc/xc.c +10
-0+ numainfo.vcpu_to_node =malloc (vcpus *sizeof (int )); + numainfo.node_mem =malloc (numanodes *sizeof (uint64_t )); +if (numanodes >1 ) + { +int vcpu_per_node, remainder; +int n; + vcpu_per_node = vcpus / numanodes; + remainder = vcpus % numanodes; + n = remainder * (vcpu_per_node +1 ); +for (i =0 ; i < vcpus; i++)
I don't know the coding style, but you seem to have two different version of it. Here you do the 'for (i= ..')
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self,
Quoted 13 lines
tools/python/xen/lowlevel/xc/xc.c +12
-0+ { +if (i < n) + numainfo.vcpu_to_node[i] = i / (vcpu_per_node +1 ); +else + numainfo.vcpu_to_node[i] = remainder + (i - n) / vcpu_per_node; + } +for (i =0 ; i < numanodes; i++) + numainfo.guest_to_host_node[i] = i %2 ; +if ( nodemem_handle !=NULL &&PyList_Check (nodemem_handle) ) + { +PyObject *item; +for ( i =0 ; i < numanodes; i++)
and here it is ' for ( i = 0 ..')'.
I've failed in the past to find the coding style so I am not exactly sure which one is correct.
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 989
Quoted 5 lines
tools/python/xen/lowlevel/xc/xc.c +5
-0+ { + item =PyList_GetItem (nodemem_handle, i); + numainfo.node_mem[i] =PyInt_AsLong (item); +fprintf (stderr,"NUMA: node %i has %lu kB\n" , i, + numainfo.node_mem[i]);
There isn't any other way to print this out? Can't you use xc_dom_printf routines?
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 997
Quoted 8 lines
tools/python/xen/lowlevel/xc/xc.c +8
-0+ } + }else { +unsigned int mempernode; +if ( nodemem_handle !=NULL &&PyInt_Check (nodemem_handle) ) + mempernode =PyInt_AsLong (nodemem_handle); +else + mempernode = (memsize <<10 ) / numanodes; +fprintf (stderr,"NUMA: setting all nodes to %i KB\n" , mempernode);
dittoo..
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 999
Quoted 1 line
tools/python/xen/lowlevel/xc/xc.c +1
-0+for (i =0 ; i < numanodes; i++)
dittoo for the coding guideline.
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 1004
Quoted 6 lines
tools/python/xen/lowlevel/xc/xc.c +6
-0+ numainfo.node_mem[i] = mempernode; + } + } + +if (xc_hvm_build_target_mem (self->xc_handle, dom, memsize, target, + &numainfo, image) !=0 )
and I guess here too
Quoted 4 lines
tools/python/xen/lowlevel/xc/xc.c +0
-0return pyxc_error_to_exception ();#if !defined(__ia64__)
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 1025
Quoted 10 lines
tools/python/xen/lowlevel/xc/xc.c +7
-0@@ -970,6 +1016,15 @@ static PyObject *pyxc_hvm_build(XcObject *self, va_hvm->apic_mode = apic; va_hvm->nr_vcpus = vcpus;memcpy (va_hvm->vcpu_online, vcpu_avail,sizeof (vcpu_avail)); + + va_hvm->num_nodes = numanodes; +if (numanodes >0 ) { +for (i =0 ; i < vcpus; i++) + va_hvm->vcpu_to_node[i] = numainfo.vcpu_to_node[i]; +for (i =0 ; i < numanodes; i++) + va_hvm->node_mem[i] = numainfo.node_mem[i] >>10 ;
Would it make sense to have 10 be #defined somewhere?
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_physinfo(XcObject *self) · line 1232
Quoted 11 lines
tools/python/xen/lowlevel/xc/xc.c +3
-1+ } +for ( i =0 , sum =0 ; i < va_hvm->length; i++ ) sum += ((uint8_t *)va_hvm)[i]; va_hvm->checksum -= sum;@@ -1174,7 +1229,7 @@ static PyObject *pyxc_physinfo(XcObject *self) nr_nodes++; } - ret_obj = Py_BuildValue("{s:i,s:i,s:i,s:i,s:i,s:i,s:l,s:l,s:l,s:i,s:s:s:s}", + ret_obj = Py_BuildValue("{s:i,s:i,s:i,s:i,s:i,s:i,s:l,s:l,s:l,s:i,s:s,s:s}",
what changed in that line? My eyes don't seem to be able to find the difference.
Quoted 22 lines
tools/python/xen/lowlevel/xc/xc.c +0
-0"nr_nodes" , nr_nodes,"max_node_id" , info.max_node_id, "max_cpu_id", info.max_cpu_id,tools/python/xen/xend/image.py +2
-1@@ -961,7 +961,8 @@ class HVMImageHandler(ImageHandler): vcpus = self.vm.getVCpuCount(), vcpu_avail = self.vm.getVCpuAvail(), acpi = self.acpi, - apic = self.apic) + apic = self.apic, + nodes = 0) rc['notes'] = { 'SUSPEND_CANCEL': 1 } rc['store_mfn'] = xc.hvm_get_param(self.vm.getDomid(),_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 1 line · Konrad Rzeszutek Wilk
On Thu, Feb 04, 2010 at 10:54:22PM +0100, Andre Przywara wrote:
Konrad, thanks for your review. Comments inline.
Quoted 15 lines
Quoted 6 lines
This patch adds a "struct
numa_guest_info" to libxc, which allows to specify a guest's NUMA topology along with the appropriate host binding.
Here the information will be filled out by the Python wrapper (I left out the libxl part for now), it will fill up the struct with sensible default values (equal distribution), only the number of guest nodes should be specified by the caller. The information is passed on to thehvm_info_table. The respective memory allocation is in another patch.Signed-off-by Andre Przywara <[email protected]>...
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 972
Quoted 8 lines
tools/python/xen/lowlevel/xc/xc.c +8
-0+if (numanodes >1 ) + { +int vcpu_per_node, remainder; +int n; + vcpu_per_node = vcpus / numanodes; + remainder = vcpus % numanodes; + n = remainder * (vcpu_per_node +1 ); +for (i =0 ; i < vcpus; i++)
Quoted 2 lines
I don't know the coding style, but you seem to have two different version of it. Here you do the 'for (i= ..')
It seems that Xen does not have a consistent coding style in this respect, I have seen both versions in Xen already. I usually do coding-style-by-copying, looking at similar nearby statements and applying the style to the new one (useful if you do code changes in Xen HV, tools, ioemu, etc.). That seemed to fail here.
Keir, is there a definite rule for the "space after brace" issue?
Quoted 18 lines
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self,
Quoted 13 lines
tools/python/xen/lowlevel/xc/xc.c +12
-0+ { +if (i < n) + numainfo.vcpu_to_node[i] = i / (vcpu_per_node +1 ); +else + numainfo.vcpu_to_node[i] = remainder + (i - n) / vcpu_per_node; + } +for (i =0 ; i < numanodes; i++) + numainfo.guest_to_host_node[i] = i %2 ; +if ( nodemem_handle !=NULL &&PyList_Check (nodemem_handle) ) + { +PyObject *item; +for ( i =0 ; i < numanodes; i++)and here it is ' for ( i = 0 ..')'.
I've failed in the past to find the coding style so I am not exactly sure which one is correct.
Quoted 8 lines
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 989
Quoted 5 lines
tools/python/xen/lowlevel/xc/xc.c +5
-0+ { + item =PyList_GetItem (nodemem_handle, i); + numainfo.node_mem[i] =PyInt_AsLong (item); +fprintf (stderr,"NUMA: node %i has %lu kB\n" , i, + numainfo.node_mem[i]);There isn't any other way to print this out? Can't you use
xc_dom_printfroutines?
Probably yes, although I am not sure whether this really belongs into upstream code, I think this one is too verbose for most of the users, so I consider this a leftover from debugging. I will remove it in the next version.
Quoted 14 lines
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 997
Quoted 9 lines
tools/python/xen/lowlevel/xc/xc.c +8
-0+ } + }else { +unsigned int mempernode; +if ( nodemem_handle !=NULL &&PyInt_Check (nodemem_handle) ) + mempernode =PyInt_AsLong (nodemem_handle); +else + mempernode = (memsize <<10 ) / numanodes; +fprintf (stderr,"NUMA: setting all nodes to %i KB\n" , mempernode);dittoo..
Quoted 1 line
+ for (i = 0; i < numanodes; i++)
dittoo for the coding guideline.
Quoted 8 lines
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 1004
Quoted 6 lines
tools/python/xen/lowlevel/xc/xc.c +6
-0+ numainfo.node_mem[i] = mempernode; + } + } + +if (xc_hvm_build_target_mem (self->xc_handle, dom, memsize, target, + &numainfo, image) !=0 )and I guess here too
I am glad that most of your objections are coding-style related ;-)
Quoted 16 lines
Quoted 4 lines
return pyxc_error_to_exception();#if !defined(__ia64__)
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_hvm_build(XcObject *self, · line 1025
Quoted 10 lines
tools/python/xen/lowlevel/xc/xc.c +7
-0@@ -970,6 +1016,15 @@ static PyObject *pyxc_hvm_build(XcObject *self, va_hvm->apic_mode = apic; va_hvm->nr_vcpus = vcpus;memcpy (va_hvm->vcpu_online, vcpu_avail,sizeof (vcpu_avail)); + + va_hvm->num_nodes = numanodes; +if (numanodes >0 ) { +for (i =0 ; i < vcpus; i++) + va_hvm->vcpu_to_node[i] = numainfo.vcpu_to_node[i]; +for (i =0 ; i < numanodes; i++) + va_hvm->node_mem[i] = numainfo.node_mem[i] >>10 ;Would it make sense to have 10 be #defined somewhere?
I think it is not worth, since it is just the conversion from MB to KB. After all it maybe wiser to use a consistent unit in all parts of the code. Will think about it.
Quoted 10 lines
Quoted 10 lines
tools/python/xen/lowlevel/xc/xc.c +2
-0+ } +for ( i =0 , sum =0 ; i < va_hvm->length; i++ ) sum += ((uint8_t *)va_hvm)[i]; va_hvm->checksum -= sum;@@ -1174,7 +1229,7 @@ static PyObject *pyxc_physinfo(XcObject *self) nr_nodes++; }
Quoted 5 lines
tools/python/xen/lowlevel/xc/xc.c static PyObject *pyxc_physinfo(XcObject *self) · line 1232
Quoted 2 lines
tools/python/xen/lowlevel/xc/xc.c +1
-1- ret_obj = Py_BuildValue("{s:i,s:i,s:i,s:i,s:i,s:i,s:l,s:l,s:l,s:i,s:s:s:s}", + ret_obj = Py_BuildValue("{s:i,s:i,s:i,s:i,s:i,s:i,s:l,s:l,s:l,s:i,s:s,s:s}",what changed in that line? My eyes don't seem to be able to find the difference.
The last comma in the plus line was a colon in the minus line.
The Python doc says that these delimiters are ignored by the parser and are just for the human eye. I was confused on the first glance and found that the next to last colon is wrong. Actually it does not belong in this patch, but I didn't found it worth to be a separate patch.
Regards,
Andre.
Signature · 9 lines
Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448 3567 12 ----to satisfy European Law for business letters: Advanced Micro Devices GmbH Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632
Quoted 9 lines · Andre Przywara
Quoted 2 lines
I don't know the coding style, but you seem to have two different version of it. Here you do the 'for (i= ..')
It seems that Xen does not have a consistent coding style in this respect, I have seen both versions in Xen already. I usually do coding-style-by-copying, looking at similar nearby statements and applying the style to the new one (useful if you do code changes in Xen HV, tools, ioemu, etc.). That seemed to fail here.
Keir, is there a definite rule for the "space after brace" issue?
Follow the style of the file or module you edit. The style I prefer is followed in most 'new' (as opposed to from-Linux) files in the hypervisor itself, like xmalloc.c, page_alloc.c, x86_emulate.c, and loads of others. Outside the hypervisor itself, I can't be bothered to police it and some others seem to have intransigent opinions on the right-way-to-write-code. As long as there is consistency at least on a per-file basis, personally I can live with whatever.
-- Keir