Re: [hwloc-users] Finding closest host bridge

The bridge cannot be "not connected to anything". All objects have a parent (and are a child of that parent) except the very-top root object. Theoretically, the bridge could be connected anywhere. In practice it's connected to a NUMA node, a root object, or (rarely) a group of numa nodes. The

Re: [hwloc-users] CPU info on ARM

Can you send their /proc/cpuinfo ? It looks like all ARM platforms have very similar cpuinfo files in Linux, so I expect something similar to what's below, but maybe we'll see better which fields are interesting. Brice Le 28/01/2014 18:38, Jeff Hammond a écrit : > I don't know the answer but

Re: [hwloc-users] CPU info on ARM

I don't know the answer but I'm happy to test on my ARM systems if you have an experiment to perform. Right now, I have an NVIDIA Kayla board and a Parallella board, both of which are ARMv7. Jeff On Tue, Jan 28, 2014 at 6:51 AM, Jeff Squyres (jsquyres) wrote: > I passed

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Le 28/01/2014 14:31, Brice Goglin a écrit : > Le 28/01/2014 13:00, Samuel Thibault a écrit : >> Brice Goglin, le Tue 28 Jan 2014 12:46:24 +0100, a écrit : >>> 42: xchg %ebx,%rbx >>> >>> I guess having both ebx and rbx on these lines isn't OK. On Linux, I get >>> rsi instead of ebx, no problem.

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Le 28/01/2014 13:00, Samuel Thibault a écrit : > Brice Goglin, le Tue 28 Jan 2014 12:46:24 +0100, a écrit : >> 42: xchg %ebx,%rbx >> >> I guess having both ebx and rbx on these lines isn't OK. On Linux, I get >> rsi instead of ebx, no problem. >> >> Samuel, any idea? > Mmm, IIRC, "unsigned long"

Re: [hwloc-users] CPU info on ARM

I passed this on to my OMPI ARM contact (Leif Lindholm). Here's what he said: "It gets a bit trickier on ARM... since we may also have (implementation time) configurable cache sizes and also big.LITTLE (different processor models executing in the same SMP system)." He passed the

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Brice Goglin, le Tue 28 Jan 2014 12:46:24 +0100, a écrit : > 42: xchg %ebx,%rbx > > I guess having both ebx and rbx on these lines isn't OK. On Linux, I get > rsi instead of ebx, no problem. > > Samuel, any idea? Mmm, IIRC, "unsigned long" on windows may not be 64bit but 32bit? Perhaps we

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Le 28/01/2014 09:57, Brice Goglin a écrit : > I will debug a bit more to see if it's actually a 64bit cpuid problem > on windows. The x86 backend is entirely disabled in the 64bit windows build because configure fails to compile the cpuid assembly (in my mingw64 with gcc 4.7). It says: 40:

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Le 28/01/2014 09:46, Robin Scher a écrit : > Hi, thanks for responding. > > The CPUModel is definitely available on this machine. A 32 bit process > on the same machine correctly finds the model name using code that > calls the cpuid inline assembly to get it, and the machine itself is a > VM

Re: [hwloc-users] Having trouble getting CPU Model string on Windows 7 x64

Hi, thanks for responding. The CPUModel is definitely available on this machine. A 32 bit process on the same machine correctly finds the model name using code that calls the cpuid inline assembly to get it, and the machine itself is a VM running on a Mac, and I get the same model name from

[hwloc-users] CPU info on ARM

Hello, Is anybody familiar with ARM CPUs? I am adding more CPU information because Intel needs more: CPUVendor=GenuineIntel CPUModel=Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz CPUModelNumber=45 CPUFamilyNumber=6 Would something similar be useful for ARM? What are the fields below from