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]
Date:	Wed, 19 Dec 2012 16:07:19 +0100
From:	Jiri Olsa <>
Cc:	Corey Ashford <>,
	Frederic Weisbecker <>,
	Ingo Molnar <>,
	Namhyung Kim <>,
	Paul Mackerras <>,
	Peter Zijlstra <>,
	Arnaldo Carvalho de Melo <>
Subject: [RFC 0/3] perf tests: Adding precise event attribute test

as per issues with precise attribute [1], adding simple test to
catch it next time. 

Patch 2 adds sysfs 'precise' attribute containing maximum value
for perf_event_attr::precise_ip.

Patch 3 adds simple test checking the attribute and creating cycle
events with all possible precise values.

I based this on revert (Patch 1) discussed in [1]. I'm not sure
this revert will tak place at the end, but I wanted to get some
feedback on the 'precise' attribute first.

Attached patches:
  1/3 Revert "perf: Require exclude_guest to use PEBS - kernel side enforcement"
  2/3 perf x86: Add precise sysfs attribute
  3/3 perf tests: Add precise event attribute test



Cc: Corey Ashford <>
Cc: Frederic Weisbecker <>
Cc: Ingo Molnar <>
Cc: Namhyung Kim <>
Cc: Paul Mackerras <>
Cc: Peter Zijlstra <>
Cc: Arnaldo Carvalho de Melo <>
 arch/x86/kernel/cpu/perf_event.c | 38 ++++++++++++++++++++++++--------------
 tools/perf/Makefile              |  1 +
 tools/perf/tests/builtin-test.c  |  4 ++++
 tools/perf/tests/precise.c       | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 tools/perf/tests/tests.h         |  1 +
 5 files changed, 109 insertions(+), 14 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists