[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2] libxl: use xc_topologyinfo to figure out how many CPUs we actually have

To: Darrio Faggioli <raistlin@xxxxxxxx>
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 11 May 2012 12:40:07 +0100
Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx
Delivery-date: Fri, 11 May 2012 11:41:04 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Darrio Faggioli writes ("[Xen-devel] [PATCH v2] libxl: use xc_topologyinfo to 
figure out how many CPUs we actually have"):
> Within libxl_get_cpu_topology(), considering all the CPUs the hypervisor
> supports to be valid topology entries might lead to misleading and incorrect
> behaviours, e.g., the output of `xl info -n' below on a 16 cores machine:

Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v2] libxl: use xc_topologyinfo to figure out how many CPUs we actually have
  - From: Darrio Faggioli

Prev by Date: Re: [Xen-devel] [PATCH]libxl: allow to set more than 31 vcpus
Next by Date: Re: [Xen-devel] [PATCH][RESEND] qemu-xen: Intel GPU passthrough, fix OpRegion mapping (v3)
Previous by thread: [Xen-devel] [PATCH v2] libxl: use xc_topologyinfo to figure out how many CPUs we actually have
Next by thread: [Xen-devel] [xen-4.1-testing test] 12825: tolerable FAIL - PUSHED
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.