From: Adrian Hunter <adrian.hunter@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Miklos Szeredi <miklos@szeredi.hu>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
"Amir Goldstein" <amir73il@gmail.com>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH 0/3] perf/core: Fix address filter match with backing files
Date: Mon, 22 Sep 2025 08:23:42 +0300 [thread overview]
Message-ID: <be5624f8-c28d-4bd1-bc31-af8c5efd1f90@intel.com> (raw)
In-Reply-To: <20250909124222.222945-1-adrian.hunter@intel.com>
On 09/09/2025 15:42, Adrian Hunter wrote:
> Here are 3 small fixes stemming from a report that Intel PT address filters
> did not work in Docker containers:
>
> https://lore.kernel.org/linux-perf-users/aBCwoq7w8ohBRQCh@fremen.lan
>
>
> Adrian Hunter (3):
> perf/core: Fix address filter match with backing files
> perf/core: Fix MMAP event path names with backing files
> perf/core: Fix MMAP2 event device with backing files
>
> kernel/events/core.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Any comments on these?
prev parent reply other threads:[~2025-09-22 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 12:42 [PATCH 0/3] perf/core: Fix address filter match with backing files Adrian Hunter
2025-09-09 12:42 ` [PATCH 1/3] " Adrian Hunter
2025-09-09 13:24 ` Amir Goldstein
2025-09-09 12:42 ` [PATCH 2/3] perf/core: Fix MMAP event path names " Adrian Hunter
2025-09-09 13:35 ` Amir Goldstein
2025-09-09 12:42 ` [PATCH 3/3] perf/core: Fix MMAP2 event device " Adrian Hunter
2025-09-09 13:24 ` Amir Goldstein
2025-09-22 5:23 ` Adrian Hunter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be5624f8-c28d-4bd1-bc31-af8c5efd1f90@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=miklos@szeredi.hu \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox