From: Catalin Marinas <catalin.marinas@arm.com>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: "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>,
Arnaldo <acme@ghostprotocols.net>, Ingo Molnar <mingo@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Will Deacon <will.deacon@arm.com>,
Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH] perf: ARM64: wire up perf_regs and unwind support
Date: Wed, 12 Mar 2014 17:45:20 +0000 [thread overview]
Message-ID: <20140312174520.GB17308@arm.com> (raw)
In-Reply-To: <CAFrcx1=ZBWt1mak_6+=KbCFZEsaD3T_xZ8up4WBLSr6_JTkP1A@mail.gmail.com>
On Wed, Mar 12, 2014 at 01:42:51PM +0100, Jean Pihet wrote:
> Hi,
>
> On 13 February 2014 18:06, Jean Pihet <jean.pihet@linaro.org> wrote:
> > This patch hooks in the perf_regs and libunwind code for ARM64.
> > The tools/perf/arch/arm64 is created; it contains the arch specific
> > code for DWARF unwinding.
> >
> > Signed-off-by: Jean Pihet <jean.pihet@linaro.org>
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Ping on this patch. Can this one go into the perf tree?
I'm happy to take it as well if there are no objections from the perf
maintainers.
--
Catalin
next prev parent reply other threads:[~2014-03-12 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 17:06 Jean Pihet
2014-03-12 12:42 ` Jean Pihet
2014-03-12 17:45 ` Catalin Marinas [this message]
2014-03-13 10:12 ` Will Deacon
2014-03-13 10:22 ` Catalin Marinas
2014-03-13 12:01 ` Jean Pihet
2014-04-28 9:15 ` Jean Pihet
2014-04-28 9:24 ` Jiri Olsa
2014-04-28 12:32 ` Jean Pihet
2014-05-01 6:31 ` [tip:perf/core] perf tools ARM64: Wire " tip-bot for Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2014-02-03 18:17 [PATCH] perf: ARM64: wire " Jean Pihet
2014-02-12 8:46 ` Jean Pihet
2014-02-12 10:10 ` Will Deacon
2014-02-12 11:27 ` Ingo Molnar
2014-02-12 11:30 ` Will Deacon
2014-02-12 13:02 ` Arnaldo Carvalho de Melo
2014-02-12 13:09 ` Jiri Olsa
2014-02-13 17:01 ` Jean Pihet
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=20140312174520.GB17308@arm.com \
--to=catalin.marinas@arm.com \
--cc=acme@ghostprotocols.net \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=patches@linaro.org \
--cc=will.deacon@arm.com \
/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
Powered by JetHome