Christopher Samuel, le Thu 07 Apr 2011 02:14:31 +0200, a écrit :
> Are these ignorable ?
Yes. Cross-building code without the proper headers just for tests is
never going to work flawlessly :)
Samuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/11 03:17, Brice Goglin wrote:
> The Hardware Locality (hwloc) team is pleased to
> announce the first release candidate of v1.2:
I get the following warnings when doing a "make check"
on SuSE SLES10 on PPC64 and RHEL5.6 on x86-64:
CC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/11 07:05, Brice Goglin wrote:
> Actually, I am not so familiar with all these marketing
> names, so I don't really know if the "Fusion" name applies
> to Bulldozer chips, or only to the already available
> laptop-like Bobcat chips.
Hello,
What I call "GPU cores" is likely not shown by the operating systems as
"normal" cores. So hwloc would likely not show anything about them. The
new hwloc trunk has support for showing GPU devices (as long as they are
PCI devices), but we won't have any details about the cores inside these
Just wondering if anyone on this list has an AMD fusion laptop, or has
access to a machine with pre-release version of AMD Fusion CPUs?? I
would like to find out what hwloc reports when it is run on those
machines: do the GPU cores get reported as CPU cores or not reported
by hwloc at all?? I
On 04/06/2011 08:49 AM, Brice Goglin wrote:
Le 31/03/2011 18:06, Jeff Squyres a écrit :
On Mar 28, 2011, at 5:26 PM, Brice Goglin wrote:
libpci is needed to make this work. And only Linux gives you OS devices
for now (we use sysfs to translate between pci devs and os devs).
Is libpci
Le 31/03/2011 18:06, Jeff Squyres a écrit :
> On Mar 28, 2011, at 5:26 PM, Brice Goglin wrote:
>
>> libpci is needed to make this work. And only Linux gives you OS devices
>> for now (we use sysfs to translate between pci devs and os devs).
>>
> Is libpci available on all platforms? Or is
