From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@redhat.com>, Vojtech Pavlik <vojtech@suse.cz>,
Jiri Kosina <jkosina@suse.cz>, Jiri Slaby <jslaby@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] kprobes: introduce weak arch_check_ftrace_location() helper function
Date: Tue, 21 Oct 2014 14:00:46 +0200 [thread overview]
Message-ID: <20141021120046.GC4161@osiris> (raw)
In-Reply-To: <544627D0.60309@hitachi.com>
On Tue, Oct 21, 2014 at 06:30:56PM +0900, Masami Hiramatsu wrote:
> (2014/10/21 17:30), Heiko Carstens wrote:
> > Introduce weak arch_check_ftrace_location() helper function which
> > architectures can override in order to implement handling of kprobes
> > on function tracer call sites on their own, without depending on
> > common code or implementing the KPROBES_ON_FTRACE feature.
> >
> > Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>
> Thanks!
Ok, thanks!
If there are no objections, this patch and the s390 only patch will
go upstream via the s390 tree. Is that ok?
Thanks,
Heiko
next prev parent reply other threads:[~2014-10-21 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:30 [PATCH v3 0/2] s390 vs. kprobes on ftrace Heiko Carstens
2014-10-21 8:30 ` [PATCH v3 1/2] kprobes: introduce weak arch_check_ftrace_location() helper function Heiko Carstens
2014-10-21 9:30 ` Masami Hiramatsu
2014-10-21 12:00 ` Heiko Carstens [this message]
2014-10-21 12:11 ` Masami Hiramatsu
2014-10-21 13:16 ` Steven Rostedt
2014-10-21 8:30 ` [PATCH v3 2/2] s390/ftrace,kprobes: allow to patch first instruction Heiko Carstens
2014-10-21 19:58 ` [PATCH v3 0/2] s390 vs. kprobes on ftrace Vojtech Pavlik
2014-10-22 8:26 ` Heiko Carstens
2014-10-22 9:37 ` Vojtech Pavlik
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=20141021120046.GC4161@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
--cc=vojtech@suse.cz \
/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