Hello
hwloc 2.0 was released 4 years ago and this major release was painful
because it broke the ABI and significantly changed the API. I want to
avoid having users modify their code with #ifdef again. But there is at
least one good reason to break the ABI in the future (support for 32bits
Le 26/05/2021 à 15:23, Samuel Thibault a écrit :
Brice Goglin, le mer. 26 mai 2021 14:13:02 +0200, a ecrit:
os_index is already *unsigned* in the API (did you mean signed?). We cannot
change the obj->os_index back to signed now, it would break existing users.
Mmm, it wouldn't break the
Le 26/05/2021 à 14:24, Jirka Hladky a écrit :
However maybe debugging would be easier if tools printed that
special value as -1 instead of 4294967295 (I'd need to check other
tools too, lstopo takes care of some of these values, maybe not all).
I agree. So perhaps we can update
Le 26/05/2021 à 13:51, Jirka Hladky a écrit :
Hi Brice,
I would like to get your opinion on the following issue. On IBM LPAR,
kernel reports die_id and physical_package_id to be -1.
See [0]
hwloc-calc converts these values into an unsigned integer, resulting
in Socket ID 2^32-1:
r.
Brice
commit 7c159d723432e461b4e48cc2d38212913d2ba7c7
Author: Brice Goglin
Date: Mon Apr 26 20:35:42 2021 +0200
linux: fix support for NUMA node0 being oddline
Just like we didn't support offline CPU#0 until commit
7bcc273efd50536961ba16d474efca4ae163229b, we need to
Hello,
Maybe we have something that assumes that the first NUMA node on Linux
is #0. And something is wrong in the disallowed case anyway since the
NUMA node physical number is 0 instead of 2 there.
Can you run "hwloc-gather-topology lpar" and send the resulting
lpar.tar.bz2? (send it only
Hello Jirka
I don't think there's a bug here.
physical_package_id don't have to be between 0 and N-1, they just have
to be different to identify packages and cores between packages. Having
other values is uncommon on x86 but quite common on POWER at least.
core_id is even worse. They are
Hello
Starting today, we require that all hwloc commits have a Signed-off-by
line with your employer email. Our Github repo is not configured to
actually reject non-signed commits [1] , please try to include that line
so that we don't have to revert some commits later.
See what this line means
Hello
Which hwloc release are you using? Before hwloc 2.0, libnuma/numactl
devel headers were required for memory binding. The end of the output of
"configure" will tell you whether memory binding is supported when
building such an old release:
Hello
We now have a CI slave running cygwin on Windows 10. Everything should
work fine in v2.0.3. In the meantime, the only patch that you need to
add on top of what you sent earlier is:
https://github.com/open-mpi/hwloc/commit/3ac7bd3b3bddd763b2e58eff77a2104ea79230af
(for fixing
OK
I pushed your #ifdef fixes and I fixed the printf warning.
I opened 3 issues related to x86 cpuid and OpenProcess failing in lstopo
--ps. Hopefully we'll find a way to play with cygwin here for real in
the near future, and then add that config to our CI.
Brice
Le 02/10/2018 à 00:28, Marco Atzeri a écrit :
> Am 01.10.2018 um 19:57 schrieb Brice Goglin:
>> Le 01/10/2018 à 19:22, Marco Atzeri a écrit :
>>>
>>
>> Your own machine doesn't matter. None is these tests look at your CPU or
>> topology. *All* of them on all
Le 01/10/2018 à 19:22, Marco Atzeri a écrit :
>
>> Unfortunately that test script isn't easy to debug in the v2.x branch.
>> If that OpenProcess is where things fail, I assume that the line that
>> fails is "lstopo --ps". On MinGW, that code is ignored because /proc
>> doesn't exist. Does /proc
Le 01/10/2018 à 17:27, Marco Atzeri a écrit :
> Am 30.09.2018 um 20:11 schrieb Samuel Thibault:
>> Marco Atzeri, le dim. 30 sept. 2018 20:02:59 +0200, a ecrit:
>>> also adding a HWLOC_DECLSPEC on the first case distances.c:347
>>> does not solve the issue as the two declaration are not the same.
Thanks a lot, the code looks good. I pushed it to master. I'll backport
to stable branches once you'll send cpuid dumps for regression testing :)
Did you test the code by forcing hwloc's x86 backend with
HWLOC_COMPONENTS=x86? Otherwise hwloc uses the Linux backend by default
(which reads sysfs),
Hello
In case you missed the announce yesterday, hwloc 2.0.1rc1 changes the
library soname from 12:0:0 to 15:0:0. On Linux, it means that we'll now
build libhwloc.so.15 instead of libhwloc.so.12. That means any
application built for hwloc 2.0.0 will need to be recompiled against 2.0.1.
I should
configure only looks for CL/cl_ext.h before enabling the OpenCL backend.
Did it enable OpenCL on your machine?
On my VMs, there's
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenCL.framework/Versions/A/Headers/cl_ext.h
Le 27/09/2017 à 20:39, Brice Goglin a écrit :
>
> Le 27/09/2017 18:58, Samuel Thibault a écrit :
>> Hello,
>>
>> On systems with NVidia GPU devices, opencl devices don't show up in
>> lstopo. Running in debug mode shows that they are detected:
>>
>&g
Le 28/12/2017 à 19:20, Samuel Thibault a écrit :
>> we can add a hwloc env var to disable process-wide asserts.
> So I would set it for all Debian builds? (we don't have a fixed set of
> archs which are built inside qemu-user)
>
Yes, if that's OK for you.
I couldn't test since binding doesn't
Le 28/12/2017 à 16:18, Samuel Thibault a écrit :
> Samuel Thibault, on jeu. 28 déc. 2017 15:08:30 +0100, wrote:
>> Samuel Thibault, on mer. 20 déc. 2017 18:32:48 +0100, wrote:
>>> I have uploaded it to debian experimental, so when it passes NEW,
>>> various arch test results will show up on
>>>
Le 22/12/2017 à 11:42, Samuel Thibault a écrit :
> Hello,
>
> Brice Goglin, on mar. 19 déc. 2017 11:48:39 +0100, wrote:
>> + Memory, I/O and Misc objects are now stored in dedicated children lists,
>> not in the usual children list that is now only used for
:26, Samuel Thibault a écrit :
> Brice Goglin, on mer. 20 déc. 2017 18:16:34 +0100, wrote:
>> Le 20/12/2017 à 18:06, Samuel Thibault a écrit :
>>> It has only one NUMA node, thus triggering the code I patched over.
>> Well, this has been working fine for a while, since that's
Le 20/12/2017 à 18:06, Samuel Thibault a écrit :
> It has only one NUMA node, thus triggering the code I patched over.
Well, this has been working fine for a while, since that's my daily
development machine and all our jenkins slaves.
Can you give the usually requested details about the OS,
Le 20/12/2017 à 17:49, Samuel Thibault a écrit :
> Samuel Thibault, on mer. 20 déc. 2017 13:57:45 +0100, wrote:
>> Brice Goglin, on mar. 19 déc. 2017 11:48:39 +0100, wrote:
>>> The Hardware Locality (hwloc) team is pleased to announce the first
>>> beta release
/hwloc/pull/277
Make all depths *signed* ints
https://github.com/open-mpi/hwloc/pull/276
Remove the "System" object type
https://github.com/open-mpi/hwloc/pull/275
Move local_memory to NUMA node specific attrs
https://github.com/open-mpi/hwloc/pull/274
Brice
Le 26/10/2017 17
Le 27/09/2017 20:52, Brice Goglin a écrit :
> Hello
>
> hwloc was using C99 7 years ago. We had to revert that in hwloc 1.2
> because some software embedding hwloc needed to support some non-C99
> compilers. Things have changed and C99 is well supported now. So we're
> going t
Hello
Thanks a lot!
I updated the links on the website.
Note that your code should work up to 1.11.8 except for one new topology
flag added in 1.11.6.
I am not very good at Python but I could help finishing CUDA support if
you tell me what's missing and where to look.
Brice
Le 02/09/2017 00:32,
Le 29/08/2017 18:58, Samuel Thibault a écrit :
> Well, for coherency only, if you prefer long command-lines there, I'm
> fine with it.
That's actually the difference I like between lstopo --ps and hwloc-ps.
Few details but nice output for humans in the former. More details in a
machine-readable
Contrary to lstopo, hwloc-ps has no problem with long command-lines.
What's the point of shortening to comm here?
Brice
Le 29/08/2017 18:27, 'Gitdub ' a écrit :
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the
Hello
Open MPI currently uses hwloc by "embedding" hwloc.m4 in its own
configure script (instead of calling hwloc's configure script
explicitly). Is there any other project doing this?
Thanks
Brice
___
hwloc-devel mailing list
FWIW, I didn't get the commit email either, and I am pretty sure it's
not the first time it happens. There are no archives for this ML, do we
have a way to see the logs of the emailing script that runs on github ?
Brice
Le 08/02/2017 16:19, Jeff Squyres (jsquyres) a écrit :
> On Feb 7, 2017,
FWIW, I am trying to remove github automatic "release" tarballs from
the github page but it actually removes the corresponding git tag.
Those releases are not autogen'ed, do not contain the doc, etc.
Users are confused when they download tarballs from github instead of
from the hwloc website.
If
NULL?
By the way, obj->complete_{cpuset,nodeset} is also something we could
drop and just have a topology->complete_{cpuset,nodeset} saying "by the
way, there are others resources that we don't know much about, are
offline, ...".
Brice
>>
>> HTH
>> Ralph
Hello
Based on recent discussion about hwloc_topology_load() being slow on
some "large" platforms (almost 1 second on KNL), here's a new feature
proposal:
We've been recommending the use of XML to avoid multiple expensive
discovery: Export to XML once at boot, and reload from XML for each
actual
NUMA mode setup?
>
> Thanks,
> Swati
>
> On Monday, September 26, 2016, Brice Goglin <brice.gog...@inria.fr
> <mailto:brice.gog...@inria.fr>> wrote:
>
> Hello
>
> If there's no NUMA node object in your hwloc topology, it means
> your machine i
Hello
If there's no NUMA node object in your hwloc topology, it means your
machine isn't NUMA (there's a single NUMA node), or your system doesn't
report NUMA information at all (missing NUMA support in the kernel, etc).
This is an old design choice that is not convenient. So we'll change
that
Hello
I just pushed a new distances API to simplify/cleanup things in hwloc
2.0. It will be merged in git master next week unless big complains.
Details and comments in the pull request
https://github.com/open-mpi/hwloc/pull/210
Brice
___
More comments about individual changes below.
> add-ifndef-guard-around-gnu-source.patch
> diff --git a/config/hwloc.m4 b/config/hwloc.m4
> index f249713..855244d 100644
> --- a/config/hwloc.m4
> +++ b/config/hwloc.m4
> @@ -486,7 +486,9 @@ EOF])
> # program_invocation_name and __progname may
Le 05/04/2016 10:26, Samuel Thibault a écrit :
> The bug here is that that HWLOC_CHECK_DECL assumed that availability
> of the function was tested before, i.e.
>> conftest.c(96) : fatal error C1083: Cannot open include file: 'sched.h': No
>> such file or directory
> was unexpected.
>
Adding a
Le 04/04/2016 21:39, Peyton, Jonathan L a écrit :
>
> Hello everyone,
>
>
>
> I’ve been working on a build using both MSVC and the Intel Windows
> compiler (ICL). These three patches allow building of hwloc + utils.
>
>
>
> 1) add-ifndef-guard-around-gnu-source.patch – this minor change only
time), if an
> app is able to survive it's nice if not then well we have to live with that.
>
> Thanks,
> Lukas
>
>
> -Original Message-
> From: hwloc-devel [mailto:hwloc-devel-boun...@open-mpi.org] On Behalf Of
> Brice Goglin
> Sent: Tuesday, January 12, 2016 12:5
Hello
I just pushed the "type-filter" branch. It's supposed to replace the old
"ignore" API as well as ICACHES and IO topology flags in v2.0.
Main points:
* you may now enable, disable and query the "ignoring" (now called
filter) for any object type
* instruction caches and I/O don't need
This broken code is only used when a plugin fails to find core symbols.
Only happens in case of namespace issues (for instance when libhwloc is
loaded by another layer of plugin, something we advice not to do).
Thanks, I'll apply this.
Brice
Le 09/10/2015 23:04, Guy Streeter a écrit :
> I am
I applied a slightly different patch to v1.11 (nothing is needed in
master since the discovery logic is different and more generic).
thanks
Brice
Le 28/08/2015 21:53, Tannenbaum, Barry M a écrit :
>
> PCIe drives (like the Intel DC P3500/P3600/P3700) do not have a
> controller – they appear
Le 28/08/2015 21:53, Tannenbaum, Barry M a écrit :
>
> PCIe drives (like the Intel DC P3500/P3600/P3700) do not have a
> controller – they appear directly on the PCIe bus.
>
>
Ah nice, I needed access to a machine with such a disk before adding
this support.
Unfortunately, the I/O device
rs on this project?
>
>
>
> -Barry
>
>
>
> *From:*hwloc-devel [mailto:hwloc-devel-boun...@open-mpi.org] *On
> Behalf Of *Brice Goglin
> *Sent:* Monday, August 17, 2015 1:36 PM
> *To:* Hardware locality development list
> *Subject:* Re: [hwloc-devel] hwloc o
0 from the download site
> (http://www.open-mpi.org/software/hwloc/v1.11/). Would you prefer me
> to work from the git repository?
>
>
>
> -Barry
>
>
>
> *From:*hwloc-devel [mailto:hwloc-devel-boun...@open-mpi.org] *On
> Behalf Of *Brice Goglin
>
Le 14/08/2015 23:44, Tannenbaum, Barry M a écrit :
>
> I’m trying to build/use hwloc on Windows.
>
>
>
> The first question is does hwloc do anything to explore the storage
> devices on a Windows system?
>
Hello
Not yet. If I remember correctly, the main issue for I/O devices on
Windows is
Le 28/07/2015 16:23, Samuel Thibault a écrit :
> Brice Goglin, le Tue 28 Jul 2015 16:13:49 +0200, a écrit :
>> and your commit is slightly different: (s/xchg/mov/ and removed last line).
> xchg is spurious here, mov is enough. I didn't remove the last line, I
> just kept the
Le 28/07/2015 15:55, Samuel Thibault a écrit :
> Hello,
>
> Paul Hargrove, le Mon 20 Jul 2015 23:12:10 -0700, a écrit :
>> I believe the following inline x86 asm is correct and more robust than the
>> existing code that pgi appears to reject:
> Indeed, in the 32bit case, we don't need to shuffle
Maybe try this. It should disable the entire BGQ backend
cross-build-testing when Linux doesn't have enough pthread/cpuset support.
Brice
Le 21/07/2015 22:02, Paul Hargrove a écrit :
> I was, at Brice's request, trying out the hwloc-1.11.0 release on all
> sorts of x86 systems, with and
Applied a slightly better one, thanks.
https://github.com/open-mpi/hwloc/commit/6376438e558f4a1541f4bb1cef18c0e86f222821
Brice
Le 21/07/2015 19:07, Balaji, Pavan a écrit :
> Folks,
>
> We see a warning about assignment from a const string to a regular string
> (CFLAGS="-Wall -Werror").
Thanks.
Could you test this new asm on all your systems/compilers? I don't want break
that fragile code again.
Brice
Le 21 juillet 2015 08:17:06 UTC+02:00, Paul Hargrove a
écrit :
>Oops - send the wrong asm code.
>While "=S" is correct for the second constraint, I meant to
Thanks, I'll fix this. I'll try strlcpy() in case it's widely available
enough. Otherwise I'll just add the ending \0 manually.
Brice
Le 17/07/2015 12:56, Odzioba, Lukasz a écrit :
> Hi,
> Static analysis detected inappropriate use of strcpy function[1] in
> topology-linux.c.
> There are
We're basically supposed to use HWLOC_VERSION everywhere.
But that requirements was added while the line below was developed in
a branch at the same time. That's why it didn't get fixes.
I'll review the entire tree in case there's another one missing and
fix master and v1.11, thanks.
Brice
Le
Hello
I will likely release v1.11rc1 next week. The list of changes is
appended below.
For the record, the master branch is preparing hwloc v2.0 (which will
break the API), but it's still far from ready to release.
The v1.11 branch was added between v1.10 and v2.0 to release most
Le 18/05/2015 20:49, Peyton, Jonathan L a écrit :
>
> Hello Everyone,
>
>
>
> We have been developing The LLVM OpenMP runtime library project and
> were hoping to incorporate the hwloc library as the primary affinity
> mechanism. In order for this to happen though,
>
> a CMake build system
Le 12/05/2015 17:01, Peter Korsgaard a écrit :
> > Peter Korsgaard, le Tue 12 May 2015 16:09:55 +0200, a écrit :
> >> Make install contains a race condition in utils/hwloc, as both
> >> install-exec-hook (through intall-exec) and install-data trigger
> >> install-man:
>
> > I'm surprised:
Thanks.
Unfortunately we likely have the same problem under utils/lstopo where
the exec-hook needs that dependency :/
(everything was under utils/ in the past, and the dependency was
duplicated when splitting into utils/lstopo and utils/hwloc)
Brice
Le 12/05/2015 16:09, Peter Korsgaard a écrit
Le 25/03/2015 21:00, Jeff Squyres (jsquyres) a écrit :
> This has come up in multiple scenarios recently: when compiling OMPI (which
> contains hwloc 1.9.1), you get a linker error complaining about a duplicate
> symbol "Lhwloc1".
>
> Peter (CC'ed) was looking into this, but it came up again
Hello
I just pushed a new v1.11 branch. The idea is that master (future v2.0)
won't be ready for release before several months, but it contains many
changes that do not need to wait for all ABI breaks and big changes to
be ready in v2.0. So I've backported these to v1.11. The summary is
Le 07/03/2015 12:13, Lisandro Dalcin a écrit :
> OK, I finally figured out what's going on.
>
> I recently upgraded to Mac OS X Yosemite, and I did not install the
> Xcode command line tools. My /usr/include directory was missing,
> however I had /usr/bin/clang (not sure wether it is there because
Hello,
Sorry but we don't add configure checks without knowing what's causing
the problem. So far it only looks like a broken libxml install.
We cannot check for all broken installs in the world. Otherwise one day
somebody will remove printf from his libc and request a new configure
check for
Le 14/02/2015 14:44, Jeff Squyres (jsquyres) a écrit :
> I added a bunch of components into the hwloc coverity setup, as well as a
> dummy model file (so that coverity doesn't complain that hwloc is not fully
> configured).
>
> Brice: do you have a nightly coverity submission script running
Hello
When part of the machine is restricted (e.g. cgroups), we remove the
corresponding PUs from cpusets (unless the WHOLE_SYSTEM flag is given).
However, it looks like we never removed NUMA nodes from nodesets as
well, which looks strange.
That's a non-trivial change so I want to make sure
Yosemite
>> using GCC. I have the Darwin ports libxml2 installed - version 2.9.2.
>>
>>
>>> On Nov 19, 2014, at 1:28 PM, Brice Goglin <brice.gog...@inria.fr> wrote:
>>>
>>> Which version of libxml2 do you have?
>>>
>>> Brice
&g
Which version of libxml2 do you have?
Brice
Le 19/11/2014 22:26, Balaji, Pavan a écrit :
> I’m seeing the following failure with hwloc on the mac (yosemite):
>
> CC topology-xml-libxml.lo
>
Le 04/11/2014 14:59, Jeff Squyres (jsquyres) a écrit :
> If you're going to separate them from the normal "children", then how about
> naming them for what they are? E.g.:
>
> - pe_children
> - io_children
> - misc_children
OK but what does "pe" stand for? did you mean "pu" to match our PU
Hello
I am considering removing some features from hwloc since the next major
release will be called 2.0 and it deserves major changes :)
If you care about anything below, please speak up:
* the "custom" interface and hwloc-assembler tools (for assembling the
topology of multiple nodes): nobody
emoved from previous locations on make clean, etc.
If you get any problem, please report and use --disable-netloc in the
meantime?.
Brice
Le 02/10/2014 07:53, Brice Goglin a écrit :
> Hello,
>
> We're working at bringing the netloc functionality inside the main
> hwloc project. Netloc
From: hwloc-devel [hwloc-devel-boun...@open-mpi.org] on behalf of Brice
> Goglin [brice.gog...@inria.fr]
> Sent: Wednesday, October 08, 2014 12:32 AM
> To: hwloc-de...@open-mpi.org
> Subject: Re: [hwloc-devel] [PATCH] Fix code relying on nonexistent macros
>
> Applied thanks.
>
Applied thanks.
Interesting to see somebody who cares about PCi domains :)
Brice
Le 08/10/2014 07:24, James Custer a écrit :
> Commit 1e57af5 removed macros HWLOC_HAVE_PCI_FIND_CAP,
> HWLOC_HAVE_PCIDEV_DOMAIN, and HWLOC_HAVE_LIBPCIACCESS.
> However, these are still referenced in
Hello,
We're working at bringing the netloc functionality inside the main hwloc
project. Netloc focuses on network locality but it is very
tightly-coupled with hwloc since we create a global map assembling both
network and hwloc topologies. More info
http://www.open-mpi.org/projects/netloc/
The
Yes I want this, and even for the upcoming v1.10.0 :)
Brice
Le 02/10/2014 02:59, Jeff Squyres (jsquyres) a écrit :
> Errr... I got the patch slightly wrong. The one added line should include
> the ".$HWLOC_RELEASE_VERSION" at the end. You get the idea...
>
>
> On Oct 1, 2014, at 8:50 PM,
Le 24/09/2014 00:19, Pedaballe, Vineet a écrit :
> Please find my response inline.
>
> Some of the items related to hard drives & DIMM is available only with root
> privileges. We should be able to populate objects related to these items only
> when root privileges are available. Is this an
Le 23/09/2014 21:06, Pedaballe, Vineet a écrit :
> 4a. Network Adapters (Ethernet)
> a. Model
> b. Speed
Both supported and currently negociated link speed?
On Linux, we'll have to use the ethtool interface.
> c. Serial Number (if applicable)
> d. MAC address
> 4b.
Le 23/09/2014 16:46, Brice Goglin a écrit :
> Le 23/09/2014 16:38, Guy Streeter a écrit :
>> I know that udev gathers this information:
>>
>> # ll /sys/block/sda/bdi
>> lrwxrwxrwx. 1 root root 0 Sep 23 09:33 /sys/block/sda/bdi ->
>> ../../../../../../../../vi
Le 23/09/2014 16:38, Guy Streeter a écrit :
> I know that udev gathers this information:
>
> # ll /sys/block/sda/bdi
> lrwxrwxrwx. 1 root root 0 Sep 23 09:33 /sys/block/sda/bdi ->
> ../../../../../../../../virtual/bdi/8:0
> # grep SERIAL '/run/udev/data/b8:0'
>
Le 22/09/2014 23:28, Ralph Castain a écrit :
>
> I believe that is what we are requesting - and to be clear, Intel is
> proposing to develop and contribute this feature. We'd like to add attributes
> to the objects to record:
>
> * memory - the serial number and model number of the DIMMs
>
> *
Arg, this strncasecmp mess was really a pandora box. I hope this fix is
the last one.
Thanks
Brice
Le 08/09/2014 20:31, Ralph Castain a écrit :
> Hey guys
>
> With the Intel compilers, you get an error in 1.9.1 relating to your
> private/misc.h header:
>
> In file included from bitmap.c(12):
>
een using 1.9 in mpich and that works
> fine. We were attempting to slurp in the bug fixes in 1.9.1, and hence were
> testing it. Can 1.9.2 be released with this fix?
>
> Thanks,
>
> — Pavan
>
> On Sep 4, 2014, at 9:57 AM, Brice Goglin <brice.gog...@inria.fr> wrote:
Le 04/09/2014 16:39, Balaji, Pavan a écrit :
> ./configure CFLAGS='-Werror-implicit-function-declaration
> -D_POSIX_C_SOURCE=200112L’
Hello,
Looks like we need
Did this config work in the past? I am getting a failure because of
putenv() in lstopo.c later, and that code didn't change recently.
Hello,
I am planning to release v1.10 soon. We don't have any new big feature,
just random improvements everywhere, see below. If there's something
important you want now, please speak up quickly.
thanks
Brice
* API
+ hwloc_distrib() does not ignore any objects anymore when there are
too
ed in 1.7.1.
Brice
commit 7491172a4754b0e198f699cb31b7c65c59ac4df6
Author: Brice Goglin <brice.gog...@inria.fr>
List-Post: hwloc-devel@lists.open-mpi.org
Date: Wed May 15 08:15:49 2013 +
Stop embedding libltdl, always use the system-wide libltdl
The ltdl embedding caused problems to the hwloc embedd
Hello,
Can you elaborate how you would use this?
The intend of the current behavior is:
1) if the target task already runs, use "hwloc-bind --pid --get"
without any command since you have pid already
2) you just want to check whether the upcoming binding works, so you
just do something like
Hello,
I ignored hunks #1 and #2 (mpich specific), applied hunks in diff.c,
ignored in topology-linux.c (don't see why they are needed), applied
topology-xml.c, applied a simpler change to topology.c. Things are in trunk.
Brice
Le 07/07/2014 20:06, Balaji, Pavan a écrit :
> Folks,
>
> We are
This code is only built on Linux so I am not sure we're more portable than OMPI
here. The oldest Linux we've tested bwloc on is likely your machines ;)
Brice
On 24 avril 2014 00:48:46 UTC+02:00, Paul Hargrove wrote:
>Since I suspect hwloc may run on *more* platforms than
Same error.
Brice
Le 07/04/2014 23:43, Jeff Squyres (jsquyres) a écrit :
> How about:
>
> tar c -C /home/ci/hwloc-gitclone -h -f - doc/doxygen-doc | tar x -C
> /home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
>
>
>
> On Apr 7, 2014, at 5:36 PM, Brice Goglin <bric
Works on my Linux but fails on Solaris:
tar -c -C /home/ci/hwloc-gitclone -h -f - doc/doxygen-doc | tar -x -C
/home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
tar: /dev/rmt/0: No such file or directory
Le 07/04/2014 23:29, Jeff Squyres (jsquyres) a écrit :
> --- a/config/distscript.sh
> +++
So you just broke my make dist :/
I don't have MacOS to test things. If rsync or tar or whatever can
dereference symlinks, that'll work for me.
commit 0ebeff689e9414d5eedbf53e7c8697a3af5e4b72
Author: Brice Goglin <brice.gog...@inria.fr>
List-Post: hwloc-devel@lists.open-mpi.org
Date: F
st" works fine.
>
> But "make distcheck" fails when it runs "make dist" in the subdir of the
> expanded tarball fails because doc/doxygen-doc doesn't exist in there.
>
>
> On Apr 7, 2014, at 3:57 PM, Brice Goglin <brice.gog...@inria.fr> wrote:
>
>&g
2]: *** [distdir] Error 2
> make[1]: *** [dist] Error 2
> make: *** [distcheck] Error 1
> -
>
> Is this expected / has this been broken for a while?
>
>
>
>
> On Mar 31, 2014, at 1:42 AM, Brice Goglin <brice.gog...@inria.fr> wrote:
>
>> Le 31/03/2014 00:57,
Le 31/03/2014 00:57, Christopher Samuel a écrit :
> On 30/03/14 02:04, Ralph Castain wrote:
>
> > turns out that some linux distro's automatically set LS_COLORS in
> > your environment when running old versions of csh/tcsh via their
> > default dot files
>
> For example RHEL6 does this..
Looks
Jeff,
Where does this LS_COLORS variable come from? Who is setting it?
Brice
Le 27/03/2014 11:45, MPI Team a écrit :
> The branch, master has been updated
>via 0e6fe307c10d47efee3fb95c50aee9c0f01bc8ec (commit)
> from 00f85033d269e2c312370bb24043f92a92dff7e3 (commit)
>
> Those
Hello,
I am thinking of releasing hwloc v1.9 in the next week. The current NEWS
is appended below, as well as what's also queued for a v1.8.2 (that may
or may not ever exist). We don't have anything wonderful, just tiny bits
everywhere.
Does anybody need anything else?
The only remaining thing in
Le 13/02/2014 12:03, Andrew Cooper a écrit :
>> Do you want to merge something in hwloc soon?
> Would you mind merging your two patches that I am carrying?
>
> "plugins: export hwloc_alloc_root_sets()"
> "plugins: cleanup hwloc_setup_pu_level() and export it to plugins"
>
> Neither of them are
Le 29/01/2014 18:47, Andrew Cooper a écrit :
> This would be nice, although it would involve some more selection on the
> exclusions. Currently, running Xen excludes all other cpu detection
> methods as they are more likely than not to be wrong.
>
> One solution to this would be to have a
I've been thinking about how to use the cpuid hypercall.
Right now the x86 backend does
foreach proc
bind on this proc
do a lot of cpuid calls
It would do instead
foreach proc
cpuid hypercall on this proc
So we would
1) add a cpuid(topology, cpu, inputbuffer, outputbuffer) hook pointer in
=0xc09;revision=9
The drawback is that you'd have to parse CPUModelNumber to extract
family and model.
I am not sure which one is best.
Brice
Le 28/01/2014 00:09, Brice Goglin a écrit :
> Hello,
> I have some code that seems to work. Here's what it reports below.
> Does that look
Should be easy on Linux, sure.
The model name is already known as CPUModel in hwloc.
We should likely add CPUVendor (would be GenuineIntel or AuthenticAMD),
CPUFamily (or CPUFamilyNumber if there's a name for these families?) and
CPUModelNumber ?
Brice
Le 23/01/2014 19:09, Ralph Castain a
1 - 100 of 616 matches
Mail list logo