papi_native_avail not reporting events for lazy init components

Issue #99 resolved
john.rodgers created an issue

Using a build containing the updates from PR 236, I’m finding that papi_native_avail is unable to report/list events for components that use the new forced lazy initialization logic. Source of issue: component is marked as disabled with the new error code -26 PAPI_EDELAY_INIT.

Quick testing has shown that propagating the force_lazy_init() logic from src/utils/papi_component_avail.c to just prior to the PAPI_get_component_info (line 579) call fixes the issue.

Comments (3)

  1. Giuseppe Congiu

    That seems to be caused by line 582 of papi_native_avail.c which should be changed to:

    if (component->disabled && component->disabled != PAPI_EDELAY_INIT) continue;
    

  2. john.rodgers reporter

    Tested suggested change, producing desired results for cuda, nvml, rocm, and rocm_smi components.

    Thanks Giuseppe!

  3. Log in to comment