Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Jiri Hladky
Hi Brice, thanks for pointing this out! Using the plugins is the way to go. Jirka On Tue, Apr 1, 2014 at 12:58 PM, Brice Goglin wrote: > That's exactely why we have plugin support. You can pass > --enable-plugins so that all plugin-able backends are built as separate > hwloc_foo.so files tha

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

2014-04-01 Thread Yury Vorobyov
Current BIOS version could be improperly detecting CPUs, which engineering samples of 6348 (all characteristics are same). On Tue, Apr 1, 2014 at 6:59 PM, Yury Vorobyov wrote: > The BIOS has latest version. If I should check some BIOS information, I > have access to hardware. Tell me what varia

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

2014-04-01 Thread Brice Goglin
Hello, Before we talk about the BIOS again, try export HWLOC_COMPONENTS=-linux lstopo This will query topology information from the processor cpuid instruction instead of from Linux (in case your kernel is too old) Brice Le 01/04/2014 14:59, Yury Vorobyov a écrit : > The BIOS has lates

Re: [hwloc-users] misleading cache size on AMD Opteron 6348?

2014-04-01 Thread Yury Vorobyov
The BIOS has latest version. If I should check some BIOS information, I have access to hardware. Tell me what variables from SMBIOS you want to see? On Fri, Jan 31, 2014 at 1:07 PM, Brice Goglin wrote: > Hello, > > Your BIOS reports invalid L3 cache information. On these processors, the > L3 i

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Brice Goglin
That's exactely why we have plugin support. You can pass --enable-plugins so that all plugin-able backends are built as separate hwloc_foo.so files that are used only when available/loaded at runtime. Then you can put them in different packages and hwloc will only load the available ones. For inst

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Jiri Hladky
Hi Brice, I'm sorry for the double report. Now when you wrote it I remember that I have reported it:-) Thanks for fixing the man page. I have one more question: RHEL has splitted hwloc into 2 subpackages * hwloc * hwloc-gui (it contains merely lstopo) The former one does not need any X11 depend

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Brice Goglin
Le 01/04/2014 10:43, Jiri Hladky a écrit : > Hi Brice, > > I see some compiler warnings when building rpm package for Fedora: > > topology-windows.c: In function 'hwloc_win_get_VirtualAllocExNumaProc': > topology-windows.c:338:30: warning: assignment from incompatible > pointer type [enabled by def

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Jiri Hladky
Hi Brice, no more warning detected with rpmlint hwloc-gui.x86_64: W: manual-page-warning /usr/share/man/man1/lstopo.1.gz 66: cannot use a space as a starting delimiter Thanks Jirka On Wed, Mar 26, 2014 at 12:48 PM, Brice Goglin wrote: > The Hardware Locality (hwloc) team is pleased to announc

Re: [hwloc-users] [hwloc-announce] Hardware locality (hwloc) v1.9 released

2014-04-01 Thread Jiri Hladky
Hi Brice, I see some compiler warnings when building rpm package for Fedora: topology-windows.c: In function 'hwloc_win_get_VirtualAllocExNumaProc': topology-windows.c:338:30: warning: assignment from incompatible pointer type [enabled by default] topology-windows.c:343:28: warning: assignment fr