mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>, 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>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section
Date: Thu, 12 Sep 2013 14:19:53 +0200	[thread overview]
Message-ID: <20130912121953.GX31370@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFrcx1mQ-P7byYfqP-0bYabUzTDeSWyHFx2FJQ6wQLYEcV_Pxw@mail.gmail.com>

On Thu, Sep 12, 2013 at 02:07:23PM +0200, Jean Pihet wrote:
> Hi,
> 
> -- Adding more maintainers in the To: list --
> 
> Ping about the patch set, is this one acceptable for mainline?

The below looks to be mostly ARM bits and I would suspect Will to take
care of them.

> On 9 September 2013 12:00, Jean Pihet <jean.pihet@linaro.org> wrote:

> >  arch/arm/Kconfig                        |  2 +
> >  arch/arm/include/uapi/asm/Kbuild        |  1 +
> >  arch/arm/include/uapi/asm/perf_regs.h   | 23 +++++++++++
> >  arch/arm/kernel/Makefile                |  1 +
> >  arch/arm/kernel/perf_regs.c             | 30 ++++++++++++++
> >  tools/perf/arch/arm/Makefile            |  3 ++
> >  tools/perf/arch/arm/include/perf_regs.h | 54 +++++++++++++++++++++++++
> >  tools/perf/arch/arm/util/unwind.c       | 48 ++++++++++++++++++++++
> >  tools/perf/config/Makefile              |  9 +++--
> >  tools/perf/util/unwind.c                | 71 +++++++++++++++++++++++++--------

This one looks to be generic code, Acme who do we want to look at that?

> >  10 files changed, 223 insertions(+), 19 deletions(-)
> >  create mode 100644 arch/arm/include/uapi/asm/perf_regs.h
> >  create mode 100644 arch/arm/kernel/perf_regs.c
> >  create mode 100644 tools/perf/arch/arm/include/perf_regs.h
> >  create mode 100644 tools/perf/arch/arm/util/unwind.c
> >
> > --
> > 1.7.11.7
> >

  reply	other threads:[~2013-09-12 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 10:00 Jean Pihet
2013-09-09 10:00 ` [PATCH 1/3] ARM: perf: add support for perf registers API Jean Pihet
2013-09-09 10:00 ` [PATCH 2/3] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-09 10:00 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-10 19:14   ` David Ahern
2013-09-10 19:38     ` Jean Pihet
2013-09-12 12:38   ` Jiri Olsa
2013-09-10  7:29 ` [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-12 12:07 ` Jean Pihet
2013-09-12 12:19   ` Peter Zijlstra [this message]
2013-09-12 12:28     ` Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2013-09-04 18:04 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=20130912121953.GX31370@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --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@redhat.com \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®