Hi Samuel, I'm using hwloc-1.3a1r3606. Now hwloc_get_last_cpu_location() works well:
thread 0 bind: 0x00000008 as core number 3 thread 1 bind: 0x00000800 as core number 11 but hwloc_linux_get_tid_cpubind() has still some problems because after binding one thread on just one core it give me: thread 0 bind: 0x00000008 as core number 3 thread 1 bind: "0x00ffffff" as all available cores!! 2011/8/10 Gabriele Fatigati <g.fatig...@cineca.it> > Ok, > > thanks! > > 2011/8/10 Samuel Thibault <samuel.thiba...@inria.fr> > >> Samuel Thibault, le Wed 10 Aug 2011 16:24:39 +0200, a écrit : >> > Gabriele Fatigati, le Wed 10 Aug 2011 16:13:27 +0200, a écrit : >> > > there is something wrong. I'm using two thread, the first one is bound >> on >> > > HWLOC_OBJ_PU number 2, the second one on HWLOC_OBJ_PU number 10, >> > >> > It seems that hwloc_linux_get_tid_last_cpu_location erroneously assume >> > that /proc/self/stat points to its own thread state indeed, we need to >> > fix that. >> >> This should now be fixed in the trunk and the v1.2 branch. You can >> either upgrade from svn, or wait for this night's snapshot. >> >> Samuel >> _______________________________________________ >> hwloc-users mailing list >> hwloc-us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-users >> > > > > -- > Ing. Gabriele Fatigati > > HPC specialist > > SuperComputing Applications and Innovation Department > > Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy > > www.cineca.it Tel: +39 051 6171722 > > g.fatigati [AT] cineca.it > -- Ing. Gabriele Fatigati HPC specialist SuperComputing Applications and Innovation Department Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy www.cineca.it Tel: +39 051 6171722 g.fatigati [AT] cineca.it
