From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 2/5] powerpc: kretprobes: override default function entry offset
Date: Tue, 14 Mar 2017 10:18:39 -0300 [thread overview]
Message-ID: <20170314131839.GD3089@kernel.org> (raw)
In-Reply-To: <87a88vuf9p.fsf@concordia.ellerman.id.au>
Em Thu, Mar 09, 2017 at 05:37:38PM +1100, Michael Ellerman escreveu:
> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:
> > On 2017/03/08 11:29AM, Arnaldo Carvalho de Melo wrote:
> >> > I wasn't sure if you were planning on picking up KPROBES_ON_FTRACE for
> >> > v4.11. If so, it would be good to take this patch through the powerpc
> >> > tree. Otherwise, this can go via Ingo's tree.
> >>
> >> If you guys convince Ingo that this should go _now_, then just cherry
> >> pick what was merged into tip/perf/core that is needed for the arch
> >> specific stuff and go from there.
> >
> > Ok, in hindsight, I think Michael's concern was actually for v4.12
>
> Yes I was talking about 4.12, sorry I thought that was implied :)
>
> > itself, in which case this particular patch can go via powerpc tree,
> > while the rest of the patches in this series can go via your tree.
> >
> > Michael?
>
> Yeah I think that's the easiest option. The function will be temporarily
> unused until the two trees are merged, but I think that's fine.
Ok, done that, now compile testing building it in my
multi-distro/x-build containers.
- Arnaldo
next prev parent reply other threads:[~2017-03-14 13:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 8:26 [PATCH v5 0/5] kretprobe fixes Naveen N. Rao
2017-03-08 8:26 ` [PATCH v5 1/5] trace/kprobes: fix check for kretprobe offset within function entry Naveen N. Rao
2017-03-16 16:34 ` [tip:perf/core] trace/kprobes: Fix " tip-bot for Naveen N. Rao
2017-03-08 8:26 ` [PATCH v5 2/5] powerpc: kretprobes: override default function entry offset Naveen N. Rao
2017-03-08 10:43 ` Michael Ellerman
2017-03-08 14:24 ` Naveen N. Rao
2017-03-08 14:29 ` Arnaldo Carvalho de Melo
2017-03-08 16:46 ` Naveen N. Rao
2017-03-09 6:37 ` Michael Ellerman
2017-03-09 8:03 ` Naveen N. Rao
2017-03-14 13:18 ` Arnaldo Carvalho de Melo [this message]
2017-03-15 9:15 ` Naveen N. Rao
2017-04-24 22:47 ` [v5,2/5] " Michael Ellerman
2017-03-08 8:26 ` [PATCH v5 3/5] perf: probe: factor out the ftrace README scanning Naveen N. Rao
2017-03-15 18:42 ` [tip:perf/core] perf probe: Factor " tip-bot for Naveen N. Rao
2017-03-08 8:26 ` [PATCH v5 4/5] perf: kretprobes: offset from reloc_sym if kernel supports it Naveen N. Rao
2017-03-15 18:43 ` [tip:perf/core] perf kretprobes: Offset " tip-bot for Naveen N. Rao
2017-03-08 8:26 ` [PATCH v5 5/5] perf: powerpc: choose local entry point with kretprobes Naveen N. Rao
2017-03-08 10:31 ` Masami Hiramatsu
2017-03-08 11:39 ` Naveen N. Rao
2017-03-15 18:43 ` [tip:perf/core] perf powerpc: Choose " tip-bot for Naveen N. Rao
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=20170314131839.GD3089@kernel.org \
--to=acme@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox