Files
blis/frame/base/bli_init.c
Field G. Van Zee 453deb2906 Implemented runtime kernel management.
Details:
- Reworked the build system around a configuration registry file, named
  config_registry', that identifies valid configuration targets, their
  constituent sub-configurations, and the kernel sets that are needed by
  those sub-configurations. The build system now facilitates the building
  of a single library that can contains kernels and cache/register
  blocksizes for multiple configurations (microarchitectures). Reference
  kernels are also built on a per-configuration basis.
- Updated the Makefile to use new variables set by configure via the
  config.mk.in template, such as CONFIG_LIST, KERNEL_LIST, and KCONFIG_MAP,
  in determining which sub-configurations (CONFIG_LIST) and kernel sets
  (KERNEL_LIST) are included in the library, and which make_defs.mk files'
  CFLAGS (KCONFIG_MAP) are used when compiling kernels.
- Reorganized 'kernels' directory into a "flat" structure. Renamed kernel
  functions into a standard format that includes the kernel set name
  (e.g. 'haswell'). Created a "bli_kernels_<kernelset>.h" file in each
  kernels sub-directory. These files exist to provide prototypes for the
  kernels present in those directories.
- Reorganized reference kernels into a top-level 'ref_kernels' directory.
  This directory includes a new source file, bli_cntx_ref.c (compiled on
  a per-configuration basis), that defines the code needed to initialize
  a reference context and a context for induced methods for the
  microarchitecture in question.
- Rewrote make_defs.mk files in each configuration so that the compiler
  variables (e.g. CFLAGS) are "stored" (renamed) on a per-configuration
  basis.
- Modified bli_config.h.in template so that bli_config.h is generated with
  #defines for the config (family) name, the sub-configurations that are
  associated with the family, and the kernel sets needed by those
  sub-configurations.
- Deprecated all kernel-related information in bli_kernel.h and transferred
  what remains to new header files named "bli_arch_<configname>.h", which
  are conditionally #included from a new header bli_arch.h. These files
  are still needed to set library-wide parameters such as custom
  malloc()/free() functions or SIMD alignment values.
- Added bli_cntx_init_<configname>.c files to each configuration directory.
  The files contain a function, named the same as the file, that initializes
  a "native" context for a particular configuration (microarchitecture). The
  idea is that optimized kernels, if available, will be initialized into
  these contexts. Other fields will retain pointers to reference functions,
  which will be compiled on a per-configuration basis. These bli_cntx_init_*()
  functions will be called during the initialization of the global kernel
  structure. They are thought of as initializing for "native" execution, but
  they also form the basis for contexts that use induced methods. These
  functions are prototyped, along with their _ref() and _ind() brethren, by
  prototype-generating macros in bli_arch.h.
- Added a new typedef enum in bli_type_defs.h to define an arch_t, which
  identifies the various sub-configurations.
- Redesigned the global kernel structure (gks) around a 2D array of cntx_t
  structures (pointers to cntx_t, actually). The first dimension is indexed
  over arch_t and the inner dimension is the ind_t (induced method) for
  each microarchitecture. When a microarchitecture (configuration) is
  "registered" at init-time, the inner array for that configuration in the
  2D array is initialized (and allocated, if it hasn't been already). The
  cntx_t slot for BLIS_NAT is initialized immediately and those for other
  induced method types are initialized and cached on-demand, as needed. At
  cntx_t registration, we also store function pointers to cntx_init functions
  that will initialize (a) "reference" contexts and (b) contexts for use with
  induced methods. We don't cache the full contexts for reference contexts
  since they are rarely needed. The functions that initialize these two kinds
  of contexts are generated automatically for each targeted sub-configuration
  from cpp-templatized code at compile-time. Induced method contexts that
  need "stage" adjustments can still obtain them via functions in
  bli_cntx_ind_stage.c.
- Added new functions and functionality to bli_cntx.c, such as for setting
  the level-1f, level-1v, and packm kernels, and for converting a native
  context into one for executing an induced method.
- Moved the checking of register/cache blocksize consistency from being cpp
  macros in bli_kernel_macro_defs.h to being runtime checks defined in
  bli_check.c and called from bli_gks_register_cntx() at the time that the
  global kernel structure's internal context is initialized for a given
  microarchitecture/configuration.
- Deprecated all of the old per-operation bli_*_cntx.c files and removed
  the previous operation-level cntx_t_init()/_finalize() invocations.
  Instead, we now query the gks for a suitable context, usually via
  bli_gks_query_cntx().
- Deprecated support for the 3m2 and 3m3 induced methods. (They required
  hackery that I was no longer willing to support.)
- Consolidated the 1e and 1r packm kernels for any given register blocksize
  into a single kernel that will branch on the schema and support packing
  to both formats.
- Added the cntx_t* argument to all packm kernel signatures.
- Deprecated the local function pointer array in all bli_packm_cxk*.c files
  and instead obtain the packm kernel from the cntx_t.
- Added bli_calloc_intl(), which serves as the calloc-equivalent to to
  bli_malloc_intl(). Useful when we wish to allocate and initialize to
  zero/NULL.
- Converted existing cpp macro functions defined in bli_blksz.h, bli_func.h,
  bli_cntx.h into static functions.
2017-10-18 13:29:32 -05:00

212 lines
6.9 KiB
C

/*
BLIS
An object-based framework for developing high-performance BLAS-like
libraries.
Copyright (C) 2014, The University of Texas at Austin
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
- Neither the name of The University of Texas at Austin nor the names
of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
#include "blis.h"
#ifdef BLIS_ENABLE_PTHREADS
static pthread_mutex_t init_mutex = PTHREAD_MUTEX_INITIALIZER;
#endif
static bool_t bli_is_init = FALSE;
err_t bli_init( void )
{
err_t r_val = BLIS_FAILURE;
// If bli_is_init is TRUE, then we know without a doubt that
// BLIS is presently initialized, and thus we can return early.
if ( bli_is_init == TRUE ) return r_val;
// NOTE: if bli_is_init is FALSE, we cannot be certain that BLIS
// is ready to be initialized; it may be the case that a thread is
// inside the critical section below and is already in the process
// of initializing BLIS, but has not yet finished and updated
// bli_is_init accordingly. This boolean asymmetry is important!
// We enclose the bodies of bli_init() and bli_finalize() in a
// critical section (both with the same name) so that they can be
// safely called from multiple external (application) threads.
// Note that while the conditional test for early return may reside
// outside the critical section (as it should, for efficiency
// reasons), the conditional test below MUST be within the critical
// section to prevent a race condition of the type described above.
#ifdef BLIS_ENABLE_OPENMP
_Pragma( "omp critical (init)" )
#endif
#ifdef BLIS_ENABLE_PTHREADS
pthread_mutex_lock( &init_mutex );
#endif
// BEGIN CRITICAL SECTION
{
// Proceed with initialization only if BLIS is presently uninitialized.
// Since we bli_init() and bli_finalize() use the same named critical
// section, we can be sure that no other thread is either (a) updating
// bli_is_init, or (b) testing bli_is_init within the critical section
// (for the purposes of deciding whether to perform the necessary
// initialization subtasks).
if ( bli_is_init == FALSE )
{
// Initialize various sub-APIs.
bli_const_init();
bli_error_init();
bli_gks_init();
bli_ind_init();
bli_thread_init();
bli_memsys_init();
// After initialization is complete, mark BLIS as initialized.
bli_is_init = TRUE;
// Only the thread that actually performs the initialization will
// return "success".
r_val = BLIS_SUCCESS;
}
}
// END CRITICAL SECTION
#ifdef BLIS_ENABLE_PTHREADS
pthread_mutex_unlock( &init_mutex );
#endif
return r_val;
}
err_t bli_finalize( void )
{
err_t r_val = BLIS_FAILURE;
// If bli_is_init is FALSE, then we know without a doubt that
// BLIS is presently uninitialized, and thus we can return early.
if ( bli_is_init == FALSE ) return r_val;
// NOTE: if bli_is_init is TRUE, we cannot be certain that BLIS
// is ready to be finalized; it may be the case that a thread is
// inside the critical section below and is already in the process
// of finalizing BLIS, but has not yet finished and updated
// bli_is_init accordingly. This boolean asymmetry is important!
// We enclose the bodies of bli_init() and bli_finalize() in a
// critical section (both with the same name) so that they can be
// safely called from multiple external (application) threads.
// Note that while the conditional test for early return may reside
// outside the critical section (as it should, for efficiency
// reasons), the conditional test below MUST be within the critical
// section to prevent a race condition of the type described above.
#ifdef BLIS_ENABLE_OPENMP
_Pragma( "omp critical (init)" )
#endif
#ifdef BLIS_ENABLE_PTHREADS
pthread_mutex_lock( &init_mutex );
#endif
// BEGIN CRITICAL SECTION
{
// Proceed with finalization only if BLIS is presently initialized.
// Since we bli_init() and bli_finalize() use the same named critical
// section, we can be sure that no other thread is either (a) updating
// bli_is_init, or (b) testing bli_is_init within the critical section
// (for the purposes of deciding whether to perform the necessary
// finalization subtasks).
if ( bli_is_init == TRUE )
{
// Finalize various sub-APIs.
bli_const_finalize();
bli_error_finalize();
bli_memsys_finalize();
bli_thread_finalize();
bli_gks_finalize();
bli_ind_finalize();
// After finalization is complete, mark BLIS as uninitialized.
bli_is_init = FALSE;
// Only the thread that actually performs the finalization will
// return "success".
r_val = BLIS_SUCCESS;
}
}
// END CRITICAL SECTION
#ifdef BLIS_ENABLE_PTHREADS
pthread_mutex_unlock( &init_mutex );
#endif
#ifdef BLIS_ENABLE_PTHREADS
pthread_mutex_destroy( &init_mutex );
#endif
return r_val;
}
bool_t bli_is_initialized( void )
{
return bli_is_init;
}
// -----------------------------------------------------------------------------
void bli_init_auto( err_t* init_result )
{
*init_result = bli_init();
}
void bli_finalize_auto( err_t init_result )
{
#ifdef BLIS_ENABLE_STAY_AUTO_INITIALIZED
// If BLIS was configured to stay initialized after being automatically
// initialized, we honor the configuration request and do nothing.
// BLIS will remain initialized unless and until the user explicitly
// calls bli_finalize().
#else
// If BLIS was NOT configured to stay initialized after being automatically
// initialized, we call bli_finalize() only if the corresponding call to
// bli_init_auto() actually resulted in BLIS being initialized (indicated
// by it returning BLIS_SUCCESS); if it did nothing, we similarly do
// nothing here.
if ( init_result == BLIS_SUCCESS )
bli_finalize();
#endif
}