0af7ac53f2
* add "register" function to mca_base_component_t
* converted coll:basic and paffinity:linux and paffinity:solaris to
use this function
* we'll convert the rest over time (I'll file a ticket once all
this is committed)
* add 32 bytes of "reserved" space to the end of mca_base_component_t
and mca_base_component_data_2_0_0_t to make future upgrades
[slightly] easier
* new mca_base_component_t size: 196 bytes
* new mca_base_component_data_2_0_0_t size: 36 bytes
* MCA base version bumped to v2.0
* '''We now refuse to load components that are not MCA v2.0.x'''
* all MCA frameworks versions bumped to v2.0
* be a little more explicit about version numbers in the MCA base
* add big comment in mca.h about versioning philosophy
This commit was SVN r19073.
The following Trac tickets were found above:
Ticket 1392 --> https://svn.open-mpi.org/trac/ompi/ticket/1392
108 строки
4.1 KiB
C
108 строки
4.1 KiB
C
/*
|
|
* Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
|
|
* University Research and Technology
|
|
* Corporation. All rights reserved.
|
|
* Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
* of Tennessee Research Foundation. All rights
|
|
* reserved.
|
|
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
* University of Stuttgart. All rights reserved.
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
* All rights reserved.
|
|
* Copyright (c) 2007 Los Alamos National Security, LLC. All rights
|
|
* reserved.
|
|
* $COPYRIGHT$
|
|
*
|
|
* Additional copyrights may follow
|
|
*
|
|
* $HEADER$
|
|
*/
|
|
|
|
#include "opal_config.h"
|
|
|
|
#include <mach/mach_time.h>
|
|
|
|
#include "opal/mca/timer/timer.h"
|
|
#include "opal/mca/timer/darwin/timer_darwin.h"
|
|
#include "opal/constants.h"
|
|
|
|
opal_timer_t opal_timer_darwin_freq;
|
|
|
|
static int opal_timer_darwin_open(void);
|
|
|
|
|
|
const opal_timer_base_component_2_0_0_t mca_timer_darwin_component = {
|
|
/* First, the mca_component_t struct containing meta information
|
|
about the component itself */
|
|
{
|
|
OPAL_TIMER_BASE_VERSION_2_0_0,
|
|
|
|
/* Component name and version */
|
|
"darwin",
|
|
OPAL_MAJOR_VERSION,
|
|
OPAL_MINOR_VERSION,
|
|
OPAL_RELEASE_VERSION,
|
|
|
|
/* Component open and close functions */
|
|
opal_timer_darwin_open,
|
|
NULL
|
|
},
|
|
{
|
|
/* The component is checkpoint ready */
|
|
MCA_BASE_METADATA_PARAM_CHECKPOINT
|
|
},
|
|
};
|
|
|
|
|
|
int opal_timer_darwin_open(void)
|
|
{
|
|
mach_timebase_info_data_t sTBI;
|
|
|
|
mach_timebase_info(&sTBI);
|
|
|
|
/* mach_timebase_info() returns a fraction that can be multiplied
|
|
by the difference between two calls to mach_absolute_time() to
|
|
get the number of nanoseconds that passed between the two
|
|
calls.
|
|
|
|
On PPC, mach_timebase_info returns numer = 1000000000 and denom
|
|
= 33333335 (or possibly 25000000, depending on the machine).
|
|
mach_absolute_time() returns a cycle count from the global
|
|
clock, which runs at 25 - 33MHz, so dividing the cycle count by
|
|
the frequency gives you seconds between the interval, then
|
|
multiplying by 1000000000 gives you nanoseconds. Of course,
|
|
you should do the multiply first, then the divide to reduce
|
|
arithmetic errors due to integer math. But since we want the
|
|
least amount of math in the critical path as possible and
|
|
mach_absolute_time is already a cycle counter, we claim we have
|
|
native cycle count support and set the frequencey to be the
|
|
frequencey of the global clock, which is sTBI.denom *
|
|
(1000000000 / sTBI.numer), which is sTBI.denom * (1 / 1), or
|
|
sTBI.denom.
|
|
|
|
On Intel, mach_timebase_info returns numer = 1 nd denom = 1,
|
|
meaning that mach_absolute_time() returns some global clock
|
|
time in nanoseconds. Because PPC returns a frequency and
|
|
returning a time in microseconds would still require math in
|
|
the critical path (a divide, at that), we pretend that the
|
|
nanosecond timer is instead a cycle counter for a 1GHz clock
|
|
and that we're returning a cycle count natively. so sTBI.denom
|
|
* (1000000000 / sTBI.numer) gives us 1 * (1000000000 / 1), or
|
|
1000000000, meaning we have a 1GHz clock.
|
|
|
|
More generally, since mach_timebase_info() gives the "keys" to
|
|
transition the return from mach_absolute_time() into
|
|
nanoseconds, taking the reverse of that and multipling by
|
|
1000000000 will give you a frequency in cycles / second if you
|
|
think of mach_absolute_time() always returning a cycle count.
|
|
|
|
By the way, it's interesting to note that because these are
|
|
library functions and because of how rosetta works, a PPC
|
|
binary running under rosetta on an Intel Mac will behave
|
|
exactly like an Intel binary running on an Intel Mac.
|
|
*/
|
|
opal_timer_darwin_freq = sTBI.denom * (1000000000 / sTBI.numer);
|
|
|
|
return OPAL_SUCCESS;
|
|
}
|