linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Brian Robbins <brianrob@linux.microsoft.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf inject jit: Ignore memfd and anonymous mmap events if jitdump present
Date: Wed, 10 Aug 2022 10:05:49 -0300	[thread overview]
Message-ID: <YvOtLXXJ1O60N8Hg@kernel.org> (raw)
In-Reply-To: <20220805220645.95855-1-brianrob@linux.microsoft.com>

Em Fri, Aug 05, 2022 at 03:06:45PM -0700, Brian Robbins escreveu:
> Some processes store jitted code in memfd mappings to avoid having rwx
> mappings.  These processes map the code with a writeable mapping and a
> read-execute mapping.  They write the code using the writeable mapping
> and then unmap the writeable mapping.  All subsequent execution is
> through the read-execute mapping.
> 
> perf inject --jit ignores //anon* mappings for each process where a
> jitdump is present because it expects to inject mmap events for each
> jitted code range, and said jitted code ranges will overlap with the
> //anon* mappings.
> 
> Ignore /memfd: and [anon:* mappings so that jitted code contained in
> /memfd: and [anon:* mappings is treated the same way as jitted code
> contained in //anon* mappings.

Removed v1, applied this one.

- Arnaldo
 
> Signed-off-by: Brian Robbins <brianrob@linux.microsoft.com>
> ---
>  tools/perf/util/jitdump.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/util/jitdump.c b/tools/perf/util/jitdump.c
> index a23255773c60..4e6632203704 100644
> --- a/tools/perf/util/jitdump.c
> +++ b/tools/perf/util/jitdump.c
> @@ -845,8 +845,13 @@ jit_process(struct perf_session *session,
>  	if (jit_detect(filename, pid, nsi)) {
>  		nsinfo__put(nsi);
>  
> -		// Strip //anon* mmaps if we processed a jitdump for this pid
> -		if (jit_has_pid(machine, pid) && (strncmp(filename, "//anon", 6) == 0))
> +		/*
> +		 * Strip //anon*, [anon:* and /memfd:* mmaps if we processed a jitdump for this pid
> +		 */
> +		if (jit_has_pid(machine, pid) &&
> +			((strncmp(filename, "//anon", 6) == 0) ||
> +			 (strncmp(filename, "[anon:", 6) == 0) ||
> +			 (strncmp(filename, "/memfd:", 7) == 0)))
>  			return 1;
>  
>  		return 0;
> -- 
> 2.25.1

-- 

- Arnaldo

      parent reply	other threads:[~2022-08-10 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 22:06 [PATCH v2] perf inject jit: Ignore memfd and anonymous mmap events if jitdump present Brian Robbins
2022-08-05 22:39 ` Ian Rogers
2022-08-10 13:05 ` Arnaldo Carvalho de Melo [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=YvOtLXXJ1O60N8Hg@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=brianrob@linux.microsoft.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).