From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf synthetic-events: save 4kb from 2 stack frames
Date: Fri, 27 Mar 2020 14:23:58 +0100 [thread overview]
Message-ID: <20200327132358.GA2114302@krava> (raw)
In-Reply-To: <20200327063651.146969-1-irogers@google.com>
On Thu, Mar 26, 2020 at 11:36:51PM -0700, Ian Rogers wrote:
> Reduce the scope of PATH_MAX sized char buffers so that the compiler can
> overlap their usage.
>
> perf_event__synthesize_mmap_events before 'sub $0x45b8,%rsp' after
> 'sub $0x35b8,%rsp'.
>
> perf_event__get_comm_ids before 'sub $0x2028,%rsp' after 'sub $0x1028,%rsp'.
nice catch.. is this actualy problem somewhere? I thought
we don't need to care that much about this in user space
jirka
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/synthetic-events.c | 46 ++++++++++++++++++------------
> 1 file changed, 27 insertions(+), 19 deletions(-)
>
> diff --git a/tools/perf/util/synthetic-events.c b/tools/perf/util/synthetic-events.c
> index 3f28af39f9c6..9ff54707bb30 100644
> --- a/tools/perf/util/synthetic-events.c
> +++ b/tools/perf/util/synthetic-events.c
> @@ -70,7 +70,6 @@ int perf_tool__process_synth_event(struct perf_tool *tool,
> static int perf_event__get_comm_ids(pid_t pid, char *comm, size_t len,
> pid_t *tgid, pid_t *ppid)
> {
> - char filename[PATH_MAX];
> char bf[4096];
> int fd;
> size_t size = 0;
> @@ -80,12 +79,16 @@ static int perf_event__get_comm_ids(pid_t pid, char *comm, size_t len,
> *tgid = -1;
> *ppid = -1;
>
> - snprintf(filename, sizeof(filename), "/proc/%d/status", pid);
> + {
> + char filename[PATH_MAX];
>
> - fd = open(filename, O_RDONLY);
> - if (fd < 0) {
> - pr_debug("couldn't open %s\n", filename);
> - return -1;
> + snprintf(filename, sizeof(filename), "/proc/%d/status", pid);
> +
> + fd = open(filename, O_RDONLY);
> + if (fd < 0) {
> + pr_debug("couldn't open %s\n", filename);
> + return -1;
> + }
> }
>
> n = read(fd, bf, sizeof(bf) - 1);
> @@ -280,7 +283,6 @@ int perf_event__synthesize_mmap_events(struct perf_tool *tool,
> struct machine *machine,
> bool mmap_data)
> {
> - char filename[PATH_MAX];
> FILE *fp;
> unsigned long long t;
> bool truncation = false;
> @@ -292,18 +294,22 @@ int perf_event__synthesize_mmap_events(struct perf_tool *tool,
> if (machine__is_default_guest(machine))
> return 0;
>
> - snprintf(filename, sizeof(filename), "%s/proc/%d/task/%d/maps",
> - machine->root_dir, pid, pid);
> +#define FILENAME_FMT_STRING "%s/proc/%d/task/%d/maps"
> + {
> + char filename[PATH_MAX];
>
> - fp = fopen(filename, "r");
> - if (fp == NULL) {
> - /*
> - * We raced with a task exiting - just return:
> - */
> - pr_debug("couldn't open %s\n", filename);
> - return -1;
> - }
> + snprintf(filename, sizeof(filename), FILENAME_FMT_STRING,
> + machine->root_dir, pid, pid);
>
> + fp = fopen(filename, "r");
> + if (fp == NULL) {
> + /*
> + * We raced with a task exiting - just return:
> + */
> + pr_debug("couldn't open %s\n", filename);
> + return -1;
> + }
> + }
> event->header.type = PERF_RECORD_MMAP2;
> t = rdclock();
>
> @@ -320,10 +326,10 @@ int perf_event__synthesize_mmap_events(struct perf_tool *tool,
> break;
>
> if ((rdclock() - t) > timeout) {
> - pr_warning("Reading %s time out. "
> + pr_warning("Reading " FILENAME_FMT_STRING " time out. "
> "You may want to increase "
> "the time limit by --proc-map-timeout\n",
> - filename);
> + machine->root_dir, pid, pid);
> truncation = true;
> goto out;
> }
> @@ -412,6 +418,8 @@ int perf_event__synthesize_mmap_events(struct perf_tool *tool,
>
> fclose(fp);
> return rc;
> +
> +#undef FILENAME_FMT_STRING
> }
>
> int perf_event__synthesize_modules(struct perf_tool *tool, perf_event__handler_t process,
> --
> 2.25.1.696.g5e7596f4ac-goog
>
next prev parent reply other threads:[~2020-03-27 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 6:36 [PATCH] perf synthetic-events: save 4kb from 2 stack frames Ian Rogers
2020-03-27 13:23 ` Jiri Olsa [this message]
2020-03-27 17:33 ` Ian Rogers
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=20200327132358.GA2114302@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@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