diff options
author | Peter Zijlstra <[email protected]> | 2015-01-23 11:19:48 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2015-01-28 13:17:35 +0100 |
commit | c3c87e770458aa004bd7ed3f29945ff436fd6511 (patch) | |
tree | 79074706175f54d333daf61cc0794aa9d76b1909 /scripts/gdb/linux/modules.py | |
parent | ef454caeb740ee4e1b89aeb7f7692d5ddffb6830 (diff) |
perf: Tighten (and fix) the grouping condition
The fix from 9fc81d87420d ("perf: Fix events installation during
moving group") was incomplete in that it failed to recognise that
creating a group with events for different CPUs is semantically
broken -- they cannot be co-scheduled.
Furthermore, it leads to real breakage where, when we create an event
for CPU Y and then migrate it to form a group on CPU X, the code gets
confused where the counter is programmed -- triggered in practice
as well by me via the perf fuzzer.
Fix this by tightening the rules for creating groups. Only allow
grouping of counters that can be co-scheduled in the same context.
This means for the same task and/or the same cpu.
Fixes: 9fc81d87420d ("perf: Fix events installation during moving group")
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Arnaldo Carvalho de Melo <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Linus Torvalds <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions