linux-kernel - Re: [PATCH V3 00/22] perf tools: Introduce an abstraction for Instruction Tracing

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 12 Dec 2014 15:53:24 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	David Ahern <dsahern@...il.com>
Cc:	Adrian Hunter <adrian.hunter@...el.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung@...il.com>,
	Paul Mackerras <paulus@...ba.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH V3 00/22] perf tools: Introduce an abstraction for
 Instruction Tracing

Em Fri, Dec 12, 2014 at 09:13:25AM -0700, David Ahern escreveu:
> On 12/12/14 6:47 AM, Adrian Hunter wrote:
> >Here is V3 of some more preparatory patches for Intel PT
> >that introduce an abstraction for Instruction tracing.

> This is an x86-Intel only feature correct? If that is the case then the code
> should be not compiled for other architectures.

My view so far is that what has been pushed for inclusion facilitates
supporting an event stream that is so huge that needs to be mapped
directly from hardware to tools, that would receive it in a special
area obtained from perf_mmap(). What comes in those events? In this
case, this Intel PT stuff, but noving (should) prevent it from being
used for similar situations for other architectures.

I wonder if we could somehow rename this from 'itrace' to some other
more meaningful name given the above understanding of this being just
a way to directly funnel events from hardware to userspace together with
perf metadata (PERF_RECORD_FORK, PERF_RECORD_MMAP, etc) + other events.

In the kernel this was called a "AUX" thing, which I also think is
vague...

- Arnaldo
--
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/