From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature
Date: Tue, 8 Oct 2013 12:47:40 +0200 [thread overview]
Message-ID: <20131008104740.GU3081@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFrcx1nDe6mhxEuU4ROJGOmGFaYtVnnhXYirkmhRb1NEecNhtw@mail.gmail.com>
On Tue, Oct 08, 2013 at 12:44:32PM +0200, Jean Pihet wrote:
> Hi,
>
> On 26 September 2013 14:48, Jiri Olsa <jolsa@redhat.com> wrote:
> > On Thu, Sep 26, 2013 at 01:36:37PM +0200, Jean Pihet wrote:
> >> The newly added dwarf unwinding feature [1] requires:
> >> . a recent version (>= 1.1) of libunwind,
> >> . libunwind to be configured with --enable-debug-frame.
> >>
> >> [1] http://www.spinics.net/lists/kernel/msg1598951.html
> >>
> >> Add the corresponding API tests in the feature check list.
> >
> > Acked-by: Jiri Olsa <jolsa@redhat.com>
> >
> > thanks,
> > jirka
>
> Thanks for the ack!
>
> Is it possible to get an ack from the perf core maintainers?
> Also, is the patch going in Will's tree?
This being a tools patch you'd have to ask acme; also I know next to
nothing about all this unwind business except that its stupid expensive
;-)
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature
Date: Tue, 8 Oct 2013 12:47:40 +0200 [thread overview]
Message-ID: <20131008104740.GU3081@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFrcx1nDe6mhxEuU4ROJGOmGFaYtVnnhXYirkmhRb1NEecNhtw@mail.gmail.com>
On Tue, Oct 08, 2013 at 12:44:32PM +0200, Jean Pihet wrote:
> Hi,
>
> On 26 September 2013 14:48, Jiri Olsa <jolsa@redhat.com> wrote:
> > On Thu, Sep 26, 2013 at 01:36:37PM +0200, Jean Pihet wrote:
> >> The newly added dwarf unwinding feature [1] requires:
> >> . a recent version (>= 1.1) of libunwind,
> >> . libunwind to be configured with --enable-debug-frame.
> >>
> >> [1] http://www.spinics.net/lists/kernel/msg1598951.html
> >>
> >> Add the corresponding API tests in the feature check list.
> >
> > Acked-by: Jiri Olsa <jolsa@redhat.com>
> >
> > thanks,
> > jirka
>
> Thanks for the ack!
>
> Is it possible to get an ack from the perf core maintainers?
> Also, is the patch going in Will's tree?
This being a tools patch you'd have to ask acme; also I know next to
nothing about all this unwind business except that its stupid expensive
;-)
next prev parent reply other threads:[~2013-10-08 10:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 11:36 [PATCH v3 0/4] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-26 11:36 ` Jean Pihet
2013-09-26 11:36 ` [PATCH 1/4] ARM: perf: add support for perf registers API Jean Pihet
2013-09-26 11:36 ` Jean Pihet
2013-09-26 11:36 ` [PATCH 2/4] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-26 11:36 ` Jean Pihet
2013-09-26 11:36 ` [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature Jean Pihet
2013-09-26 11:36 ` Jean Pihet
2013-09-26 12:48 ` Jiri Olsa
2013-09-26 12:48 ` Jiri Olsa
2013-10-08 10:44 ` Jean Pihet
2013-10-08 10:44 ` Jean Pihet
2013-10-08 10:47 ` Peter Zijlstra [this message]
2013-10-08 10:47 ` Peter Zijlstra
2013-10-08 14:15 ` Jean Pihet
2013-10-08 14:15 ` Jean Pihet
2013-10-08 14:28 ` Arnaldo Carvalho de Melo
2013-10-08 14:28 ` Arnaldo Carvalho de Melo
2013-10-08 14:31 ` Will Deacon
2013-10-08 14:31 ` Will Deacon
2013-09-26 11:36 ` [PATCH 4/4] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-26 11:36 ` Jean Pihet
2013-09-26 12:49 ` Jiri Olsa
2013-09-26 12:49 ` Jiri Olsa
2013-10-08 10:44 ` Jean Pihet
2013-10-08 10:44 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2013-09-16 9:17 [PATCH v2 0/4] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-16 9:17 ` [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature Jean Pihet
2013-09-16 9:17 ` Jean Pihet
2013-09-17 10:29 ` Will Deacon
2013-09-17 10:29 ` Will Deacon
2013-09-24 8:55 ` Jean Pihet
2013-09-24 8:55 ` Jean Pihet
2013-09-24 9:34 ` Jiri Olsa
2013-09-24 9:34 ` Jiri Olsa
2013-09-24 10:06 ` Will Deacon
2013-09-24 10:06 ` Will Deacon
2013-09-24 12:03 ` Jean Pihet
2013-09-24 12:03 ` Jean Pihet
2013-09-24 17:43 ` Jiri Olsa
2013-09-24 17:43 ` Jiri Olsa
2013-09-25 6:53 ` Jean Pihet
2013-09-25 6:53 ` Jean Pihet
2013-09-25 7:31 ` Jiri Olsa
2013-09-25 7:31 ` Jiri Olsa
2013-09-26 11:39 ` Jean Pihet
2013-09-26 11:39 ` Jean Pihet
2013-09-24 17:12 ` Arnaldo Carvalho de Melo
2013-09-24 17:12 ` Arnaldo Carvalho de Melo
2013-09-30 16:01 ` Will Deacon
2013-09-30 16:01 ` Will Deacon
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=20131008104740.GU3081@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.