Hi Vince, > > I presume that the code you referred to above is the function > check_scheduability() which is in the core component but not the uncore > component. I will try putting this code into the uncore component to see if > it handles this condition any better. It will need some adjustment because > it currently only does the start/stop/read sequence on the group leader. > That makes sense in the core component but the uncore component does > not use grouping (so we can count events from multiple pmu's at the same > time). I will need to loop through all of the events doing a start/stop/read > on each. >
When I added a modified version of check_scheduability() to the uncore component it now detects that the two events with constraint conflicts cannot be used together. This allows PAPI to return an error at add event time which is better than reporting it when trying to read the results after the test is completed. One of the changes was to remove the test if the NMI watchdog was active (if (nmi_watchdog_active) return 1) from the function bug_check_scheduability(). I am hoping that NMI only affects core events and is not important when using uncore events. Does this sound like a safe assumption to you ?? So I guess since we do not have much influence with the kernel folks, we will have to go with this PAPI kludge to get better error reporting. Thanks Gary ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
