linux-kernel - [PATCH 0/4] perf: Tasks and irq exclusion

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: <1274450715-23955-1-git-send-regression-fweisbec@gmail.com>
Date:	Fri, 21 May 2010 16:05:11 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Paul Mackerras <paulus@...ba.org>
Subject: [PATCH 0/4] perf: Tasks and irq exclusion

Hi,

The new task and irq exclusion handling can let you
confine tracing and profiling to about everything you
want.

May be the only class of event I haven't tested yet is the
breakpoints and non-tracepoint software events.
Otherwise it works fine for hardware and tracepoints.

Thanks.

(Can be pulled there if you think it's fine:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
	perf/exclusion)

Frederic Weisbecker (4):
  irq: Support to compute context on top of a given preempt_count
    offset
  perf: Add exclude_task perf event attribute
  perf: Support for irq exclusion
  perf: Support for task/softirq/hardirq exclusion on tools

 include/linux/hardirq.h        |   17 +++++++--
 include/linux/perf_event.h     |    7 +++-
 kernel/perf_event.c            |   79 ++++++++++++++++++++++++++++++++--------
 tools/perf/util/parse-events.c |   37 +++++++++++++------
 4 files changed, 107 insertions(+), 33 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/