Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.5.1rc2r4894
Start time: Thu Oct 11 21:05:00 EDT 2012
End time: Thu Oct 11 21:08:30 EDT 2012
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.6a1r4890
Start time: Thu Oct 11 21:01:02 EDT 2012
End time: Thu Oct 11 21:05:00 EDT 2012
Your friendly daemon,
Cyrador
I think I would rather do something like below, to make sure we only
modify the cpuset while discovering things.
The code builds fine on FreeBSD9 and seems to work, but my testing of
changing cpuset doesn't seem to work very well so I'd like a bit more
testing.
Brice
Index: src/topology-freebs
This patch (against r4884) fixes the issue on my system. It moves the
lstopo process to cpuset 0, which includes all the CPUs in the system.
--- r4884/hwloc-trunk.svn/tests/ports/topology-freebsd.c2012-10-02
16:13:06.0 -0600
+++ cpuset/hwloc-trunk.svn/tests/ports/topology-freebsd.
The modification of the default cpuset (to exclude CPUs 0-9) is done by our
local installation. I assume the vanilla FreeBSD 7.3 that we're based on
does not monkey with the default cpuset.
I believe modifying your own cpuset is not a privileged operation in
FreeBSD. The cpuset executable is not
Sebastian Kuzminsky wrote:
> Maybe lstopo should expand its cpuset to be fully inclusive at startup? I'll
> be happy to test patches if you want.
Brice Goglin, le Thu 11 Oct 2012 18:13:53 +0200, a écrit :
> Is the cpuset-modification a root-only operation on FreeBSD? If so lstopo
> wouldn't be ab
(forwarding your mail to the list, and replying)
Good to know that it works, thanks for testing. I released 1.5.1rc1
today, it should work fine as well.
You say that the cpuset does not contain 0-9 by default on this
hardware. This is something specific to your installation, I guess?
Nothing that
