[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150129123831.GT7220@kernel.org>
Date: Thu, 29 Jan 2015 09:38:31 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Jiri Olsa <jolsa@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Andi Kleen <andi@...stfloor.org>,
Stephane Eranian <eranian@...gle.com>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 40/42] perf callchain: Save eh/debug frame offset for
dwarf unwind
Em Thu, Jan 29, 2015 at 05:07:21PM +0900, Namhyung Kim escreveu:
> When libunwind tries to resolve callchains it needs to know the offset
> of .eh_frame_hdr or .debug_frame to access the dso. Since it calls
> dso__data_fd(), it'll try to grab dso->lock everytime for same
> information. So save it to dso_data struct and reuse it.
>
> Note that there's a window between dso__data_fd() and actual use of
> the fd. The fd could be closed by other threads to deal with the open
> file limit in dso cache code. But I think it's ok since in that case
> elf_section_offset() will return 0 so it'll be tried in next acess.
I know that you did this in the context of your multi threading
patchkit, but this seems useful even without that patckhit, i.e. this
can be cherry picked on the grounds that it speeds up things by caching
something that doesn't change, right?
I.e. I'll probably just rewrite the comment and apply it before
considering the other patches, so that other people can comment on the
other patches, etc.
- Arnaldo
> Signed-off-by: Namhyung Kim <namhyung@...nel.org>
> ---
> tools/perf/util/dso.h | 1 +
> tools/perf/util/unwind-libunwind.c | 31 ++++++++++++++++++++-----------
> 2 files changed, 21 insertions(+), 11 deletions(-)
>
> diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
> index c18fcc0e8081..323ee08d56fc 100644
> --- a/tools/perf/util/dso.h
> +++ b/tools/perf/util/dso.h
> @@ -141,6 +141,7 @@ struct dso {
> u32 status_seen;
> size_t file_size;
> struct list_head open_entry;
> + u64 frame_offset;
> } data;
>
> union { /* Tool specific area */
> diff --git a/tools/perf/util/unwind-libunwind.c b/tools/perf/util/unwind-libunwind.c
> index 7ed6eaf232b6..3219b20837b5 100644
> --- a/tools/perf/util/unwind-libunwind.c
> +++ b/tools/perf/util/unwind-libunwind.c
> @@ -266,14 +266,17 @@ static int read_unwind_spec_eh_frame(struct dso *dso, struct machine *machine,
> u64 *fde_count)
> {
> int ret = -EINVAL, fd;
> - u64 offset;
> + u64 offset = dso->data.frame_offset;
>
> - fd = dso__data_fd(dso, machine);
> - if (fd < 0)
> - return -EINVAL;
> + if (offset == 0) {
> + fd = dso__data_fd(dso, machine);
> + if (fd < 0)
> + return -EINVAL;
>
> - /* Check the .eh_frame section for unwinding info */
> - offset = elf_section_offset(fd, ".eh_frame_hdr");
> + /* Check the .eh_frame section for unwinding info */
> + offset = elf_section_offset(fd, ".eh_frame_hdr");
> + dso->data.frame_offset = offset;
> + }
>
> if (offset)
> ret = unwind_spec_ehframe(dso, machine, offset,
> @@ -287,14 +290,20 @@ static int read_unwind_spec_eh_frame(struct dso *dso, struct machine *machine,
> static int read_unwind_spec_debug_frame(struct dso *dso,
> struct machine *machine, u64 *offset)
> {
> - int fd = dso__data_fd(dso, machine);
> + int fd;
> + u64 ofs = dso->data.frame_offset;
>
> - if (fd < 0)
> - return -EINVAL;
> + if (ofs == 0) {
> + fd = dso__data_fd(dso, machine);
> + if (fd < 0)
> + return -EINVAL;
>
> - /* Check the .debug_frame section for unwinding info */
> - *offset = elf_section_offset(fd, ".debug_frame");
> + /* Check the .debug_frame section for unwinding info */
> + ofs = elf_section_offset(fd, ".debug_frame");
> + dso->data.frame_offset = ofs;
> + }
>
> + *offset = ofs;
> if (*offset)
> return 0;
>
> --
> 2.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists