From: acme@ghostprotocols.net (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature
Date: Tue, 24 Sep 2013 14:12:20 -0300 [thread overview]
Message-ID: <20130924171220.GB2634@ghostprotocols.net> (raw)
In-Reply-To: <20130917102904.GA27258@mudshark.cambridge.arm.com>
Em Tue, Sep 17, 2013 at 11:29:04AM +0100, Will Deacon escreveu:
> Arnaldo, Ingo,
>
> On Mon, Sep 16, 2013 at 10:17:32AM +0100, 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 test in the feature check list.
> >
> > Signed-off-by: Jean Pihet <jean.pihet@linaro.org>
> > ---
> > tools/perf/config/Makefile | 2 +-
> > tools/perf/config/feature-tests.mak | 11 ++++++++++-
> > 2 files changed, 11 insertions(+), 2 deletions(-)
>
> Can I have an ack for this and the following patch please?
>
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/198531.html)
>
> Then I can stick these into -next for some more exposure before I queue them
> for 3.13.
I can pick it now that Jiri kinda acked it, right Jiri?
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Will Deacon <will.deacon@arm.com>
Cc: Jean Pihet <jean.pihet@linaro.org>, Jiri Olsa <jolsa@redhat.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>,
Ingo Molnar <mingo@kernel.org>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [PATCH 3/4] perf tools: Check libunwind for availability of dwarf parsing feature
Date: Tue, 24 Sep 2013 14:12:20 -0300 [thread overview]
Message-ID: <20130924171220.GB2634@ghostprotocols.net> (raw)
In-Reply-To: <20130917102904.GA27258@mudshark.cambridge.arm.com>
Em Tue, Sep 17, 2013 at 11:29:04AM +0100, Will Deacon escreveu:
> Arnaldo, Ingo,
>
> On Mon, Sep 16, 2013 at 10:17:32AM +0100, 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 test in the feature check list.
> >
> > Signed-off-by: Jean Pihet <jean.pihet@linaro.org>
> > ---
> > tools/perf/config/Makefile | 2 +-
> > tools/perf/config/feature-tests.mak | 11 ++++++++++-
> > 2 files changed, 11 insertions(+), 2 deletions(-)
>
> Can I have an ack for this and the following patch please?
>
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/198531.html)
>
> Then I can stick these into -next for some more exposure before I queue them
> for 3.13.
I can pick it now that Jiri kinda acked it, right Jiri?
- Arnaldo
next prev parent reply other threads:[~2013-09-24 17:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Jean Pihet
2013-09-16 9:17 ` [PATCH 1/4] ARM: perf: add support for perf registers API Jean Pihet
2013-09-16 9:17 ` Jean Pihet
2013-09-16 9:17 ` [PATCH 2/4] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-16 9:17 ` 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 [this message]
2013-09-24 17:12 ` Arnaldo Carvalho de Melo
2013-09-30 16:01 ` Will Deacon
2013-09-30 16:01 ` Will Deacon
2013-09-16 9:17 ` [PATCH 4/4] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-16 9:17 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
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 ` [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
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
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=20130924171220.GB2634@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--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.