diff options
author | Rob Clark <[email protected]> | 2018-07-02 10:40:36 -0400 |
---|---|---|
committer | Rob Clark <[email protected]> | 2018-07-18 10:10:44 -0400 |
commit | 09f240eb5ff6c24471bd55770771b7755ad07bc0 (patch) | |
tree | 6029f02b6aaf2928cae8182185604a2c6d8728a2 /src/mesa | |
parent | 426f1c60bced83cd9d9d026249f7e99e44aeeae6 (diff) |
mesa: don't double incr/decr ActiveCounters
Frameretrace ends up w/ excess calls to SelectPerfMonitorCountersAMD()
which ends up re-enabling already enabled counters. Which causes
ActiveCounters[group] to be double incremented for the same counter.
This causes BeginPerfMonitorAMD() to fail.
The AMD_performance_monitor spec doesn't say that an error should be
generated in this case. So I think the safe thing to do is just safe-
guard against excess increments/decrements.
Signed-off-by: Rob Clark <[email protected]>
Diffstat (limited to 'src/mesa')
-rw-r--r-- | src/mesa/main/performance_monitor.c | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/src/mesa/main/performance_monitor.c b/src/mesa/main/performance_monitor.c index 359727777ff..253d42d989c 100644 --- a/src/mesa/main/performance_monitor.c +++ b/src/mesa/main/performance_monitor.c @@ -480,14 +480,18 @@ _mesa_SelectPerfMonitorCountersAMD(GLuint monitor, GLboolean enable, if (enable) { /* Enable the counters */ for (i = 0; i < numCounters; i++) { - ++m->ActiveGroups[group]; - BITSET_SET(m->ActiveCounters[group], counterList[i]); + if (!BITSET_TEST(m->ActiveCounters[group], counterList[i])) { + ++m->ActiveGroups[group]; + BITSET_SET(m->ActiveCounters[group], counterList[i]); + } } } else { /* Disable the counters */ for (i = 0; i < numCounters; i++) { - --m->ActiveGroups[group]; - BITSET_CLEAR(m->ActiveCounters[group], counterList[i]); + if (BITSET_TEST(m->ActiveCounters[group], counterList[i])) { + --m->ActiveGroups[group]; + BITSET_CLEAR(m->ActiveCounters[group], counterList[i]); + } } } } |