From: SourceForge.net <no...@so...> - 2004-09-13 19:17:15
|
Bugs item #964097, was opened at 2004-06-01 07:48 Message generated for change (Settings changed) made by movement You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=964097&group_id=16191 Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: John Levon (movement) Summary: handling events with event code 0x00 fails Initial Comment: Oprofile uses the event code parameter to check whether an event has been set up for monitoring. When the event code is used as a boolean to check whether the event is enabled, the code cannot handle events that has an event code of 0x00. This is true for at least the BACK_END_BUBBLE event on the itanium 2 platform. Quote John Levon: "The problem is this code: 190 for (ii = 0 ; ii < op_nr_counters ; ++ii) { 191 if (sysctl.ctr[ii].event) { We need a different way to identify an event has been set." That code is in module/ia64/op_pmu.c ---------------------------------------------------------------------- Comment By: John Levon (movement) Date: 2004-06-21 03:07 Message: Logged In: YES user_id=53034 This should be partially fixed. Note we still have a problem in that if a counter has been used previously, then disabled, we don't seem to disable it in the hardware setup properly. It's in the TODO. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=964097&group_id=16191 |