From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [RFC][PATCH] x86: ptrace: Add function argument access API
Date: Thu, 11 Oct 2018 23:01:51 -0400 [thread overview]
Message-ID: <20181011230151.25ba36f3@vmware.local.home> (raw)
In-Reply-To: <20181011230021.0a7604fa@vmware.local.home>
On Thu, 11 Oct 2018 23:00:21 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> A while ago I posted an RFC patchset for dynamic function based
> events. But Masami pointed out that this could be done with kprobes
> with minimal changes. He posted a patch set back in March
> http://lkml.kernel.org/r/152049860385.7289.14079393589900496424.stgit@devbox
> I've pulled this in locally, but haven't had the time until recently
> to look at it seriously. I even plan to talk about these changes in
> my talk at Open Source Summit in Edinburgh less than two weeks away
> (talk about conference driven development!).
> Anyway, the one patch that really needs external approval is the one
> that creates a new architecture dependent API to retrieve function
> arguments from pt_regs if the ip is at the start of the function call
> (via a breakpoint or ftrace fentry). That's this patch.
>
> Anyone have any issues with it? If not, I'm going to start doing some
> serious testing of this code and try to get it into the next merge
> window.
You can also play with the full repo here:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
branch: ftrace/kprobes
-- Steve
next prev parent reply other threads:[~2018-10-12 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 3:00 [RFC][PATCH] x86: ptrace: Add function argument access API Steven Rostedt
2018-10-12 3:01 ` Steven Rostedt [this message]
2018-10-12 16:26 ` Steven Rostedt
2018-10-12 18:21 ` Andy Lutomirski
2018-10-12 18:22 ` Steven Rostedt
2018-10-12 19:54 ` Steven Rostedt
2018-10-15 14:56 ` Masami Hiramatsu
2018-10-16 18:59 ` Steven Rostedt
2018-10-18 2:34 ` Steven Rostedt
2018-10-27 14:58 ` Steven Rostedt
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=20181011230151.25ba36f3@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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