From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: Re: [RFC PATCH] perf: workaround unaligned NEON vector load
Date: Wed, 6 Mar 2019 17:14:34 -0300 [thread overview]
Message-ID: <20190306201434.GJ30734@kernel.org> (raw)
In-Reply-To: <20190306140116.23078-1-l.stach@pengutronix.de>
Em Wed, Mar 06, 2019 at 03:01:16PM +0100, Lucas Stach escreveu:
> The mmap event buffer may end up in a location that violates the
> alignment requirements for a NEON vector load,
which are?
> which GCC generates to load consecutive values from the event
> structure. Fix this by copying the event structure into a properly
> aligned buffer.
At a minimum this would be done only for such arch (is that an arch?),
so that the rest of the world doesn't have to eat this extra cost?
What is it that perf_event_mmap_event() is doing to
mmap_event->event_id.header.size that this NEON vector load dislikes?
- Arnaldo
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> tools/perf/util/machine.c | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index 143f7057d581..ab5500e85173 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1565,37 +1565,40 @@ static int machine__process_kernel_mmap_event(struct machine *machine,
> }
>
> int machine__process_mmap2_event(struct machine *machine,
> - union perf_event *event,
> + union perf_event *event_in,
> struct perf_sample *sample)
> {
> + union perf_event event;
> struct thread *thread;
> struct map *map;
> int ret = 0;
>
> + memcpy(&event, event_in, sizeof(union perf_event));
> +
> if (dump_trace)
> - perf_event__fprintf_mmap2(event, stdout);
> + perf_event__fprintf_mmap2(&event, stdout);
>
> if (sample->cpumode == PERF_RECORD_MISC_GUEST_KERNEL ||
> sample->cpumode == PERF_RECORD_MISC_KERNEL) {
> - ret = machine__process_kernel_mmap_event(machine, event);
> + ret = machine__process_kernel_mmap_event(machine, &event);
> if (ret < 0)
> goto out_problem;
> return 0;
> }
>
> - thread = machine__findnew_thread(machine, event->mmap2.pid,
> - event->mmap2.tid);
> + thread = machine__findnew_thread(machine, event.mmap2.pid,
> + event.mmap2.tid);
> if (thread == NULL)
> goto out_problem;
>
> - map = map__new(machine, event->mmap2.start,
> - event->mmap2.len, event->mmap2.pgoff,
> - event->mmap2.maj,
> - event->mmap2.min, event->mmap2.ino,
> - event->mmap2.ino_generation,
> - event->mmap2.prot,
> - event->mmap2.flags,
> - event->mmap2.filename, thread);
> + map = map__new(machine, event.mmap2.start,
> + event.mmap2.len, event.mmap2.pgoff,
> + event.mmap2.maj,
> + event.mmap2.min, event.mmap2.ino,
> + event.mmap2.ino_generation,
> + event.mmap2.prot,
> + event.mmap2.flags,
> + event.mmap2.filename, thread);
>
> if (map == NULL)
> goto out_problem_map;
> --
> 2.20.1
--
- Arnaldo
prev parent reply other threads:[~2019-03-06 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 14:01 [RFC PATCH] perf: workaround unaligned NEON vector load Lucas Stach
2019-03-06 20:14 ` 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=20190306201434.GJ30734@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=patchwork-lst@pengutronix.de \
--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