[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80d0902f-0b38-6f03-f4a4-f6d2693d7e25@intel.com>
Date: Mon, 24 Feb 2020 15:50:13 +0200
From: Adrian Hunter <adrian.hunter@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 00/13] perf/x86: Add perf text poke events
On 12/02/20 2:49 pm, Adrian Hunter wrote:
> Hi
>
> Here are patches to add a text poke event to record changes to kernel text
> (i.e. self-modifying code) in order to support tracers like Intel PT
> decoding through jump labels, kprobes and ftrace trampolines.
>
> The first 8 patches make the kernel changes and the subsequent patches are
> tools changes.
>
> The next 4 patches add support for updating perf tools' data cache
> with the changed bytes.
>
> The last patch is an Intel PT specific tools change.
>
>
> Changes in V2:
>
> perf: Add perf text poke event
>
> Separate out x86 changes
> The text poke event now has old len and new len
> Revised commit message
>
> perf/x86: Add support for perf text poke event for text_poke_bp_batch() callers
>
> New patch containing x86 changes from original first patch
Any comments?
Powered by blists - more mailing lists