Re: [hwloc-devel] Attribute request

Assuming people will confirm that ARM information isn't so simple, I wonder where it's better to put architecture specific fields. With the proposed solution, Intel and ARM would be different: Architecture=x86_64 CPUVendor=GenuineIntel CPUModel=Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz

Re: [hwloc-devel] hwloc with Xen system support - v2

I've been thinking about how to use the cpuid hypercall. Right now the x86 backend does foreach proc bind on this proc do a lot of cpuid calls It would do instead foreach proc cpuid hypercall on this proc So we would 1) add a cpuid(topology, cpu, inputbuffer, outputbuffer) hook pointer in

Re: [hwloc-devel] hwloc with Xen system support - v2

Brice Goglin, le Wed 29 Jan 2014 16:04:54 +0100, a écrit : > We may want to make inputbuffer and outputbuffer generic enough (void* + > length) so that the model works for other architectures one day? Probably, yes. > Xen will know that they correspond to inputbuffer=one-register and >

Re: [hwloc-devel] Attribute request

I'd prefer your first option - it's easy enough to check the info objects for existence of a particular attribute. On Jan 29, 2014, at 1:12 AM, Brice Goglin wrote: > Assuming people will confirm that ARM information isn't so simple, I wonder > where it's better to put

Re: [hwloc-devel] hwloc with Xen system support - v2

On 29/01/14 15:04, Brice Goglin wrote: > I've been thinking about how to use the cpuid hypercall. > > Right now the x86 backend does > foreach proc > bind on this proc > do a lot of cpuid calls > > It would do instead > foreach proc > cpuid hypercall on this proc One alternative is to

[hwloc-devel] Create success (hwloc git dev-58-g5ef4bd1)

Creating nightly hwloc snapshot git tarball was a success. Snapshot: hwloc dev-58-g5ef4bd1 Start time: Wed Jan 29 21:01:02 EST 2014 End time: Wed Jan 29 21:03:37 EST 2014 Your friendly daemon, Cyrador