linux-kernel - [PATCH 0/2] perf/x86/intel/pt: VMX related updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20170214132416.26400-1-alexander.shishkin@linux.intel.com>
Date:   Tue, 14 Feb 2017 15:24:14 +0200
From:   Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:     Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Ingo Molnar <mingo@...hat.com>
Cc:     linux-kernel@...r.kernel.org, vince@...ter.net, eranian@...gle.com,
        Arnaldo Carvalho de Melo <acme@...radead.org>,
        Borislav Petkov <bp@...e.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Subject: [PATCH 0/2] perf/x86/intel/pt: VMX related updates

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