Jeff Squyres fec7918eea Some paffinity functions had their return status overloaded: ... * If < 0, it's an OPAL_ERR_* value * If >= 0, it's the actual output value of the function This is problematic for the OPAL_SOS stuff. This commit changes those functions to always return OPAL_* statuses and send the output value back through output parameters (like 95% of the rest of the code base). This avoids the confusion with OPAL_SOS stuff and makes paffinity work again (e.g., mpirun --bind-to-core ...). I updated all paffinitiy modules for the new function signatures, and bumped the paffinity API version up to 2.0.1. I don't think the version change will matter, though, because we'll be introducing support for hardware threads soon, which will either bump the paffinity version again or we'll replace paffinity with a new framework. This commit was SVN r23197.		2010-05-21 16:55:28 +00:00
..
configure.m4	Update Cisco copyrights for consistency	2009-10-07 22:02:32 +00:00
configure.params	Remove the compile-time proiorities for paffinity modules (they were	2010-04-19 22:14:06 +00:00
Makefile.am	Add a new "test" module to the paffinity framework that mimics a system that supports affinity when running on a Mac for development purposes. Only active if specifically called out.	2009-08-26 01:55:30 +00:00
paffinity_test_component.c	Some paffinity functions had their return status overloaded:	2010-05-21 16:55:28 +00:00
paffinity_test_module.c	Some paffinity functions had their return status overloaded:	2010-05-21 16:55:28 +00:00
paffinity_test.h	Update Cisco copyrights for consistency	2009-10-07 22:02:32 +00:00