Hi Peter, On systems where PT does not coexist with VMX operation, we silently stop scheduling in PT events while VMX is on. It is confusing to the user as what they get in return is a perf session with no PT trace. So I added a check for any preexisting VMX users to the event creation path, so that we can tell the user right off the bat that it's not going to work (2/2). Also, when we do end up with PT events and VMX coexisting, the scheduling needs to be aware of it (1/2).
Alexander Shishkin (2): perf/x86/intel/pt: Fail event scheduling on conflict with VMX perf/x86/intel/pt: Fail event creation if VMX operation is on arch/x86/events/intel/pt.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) -- 2.11.0
