From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Miroslav Benes <mbenes@suse.cz>,
Thomas Gleixner <tglx@linutronix.de>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH 0/3 v6] ftrace: Add access to function arguments for all callbacks
Date: Fri, 13 Nov 2020 09:07:33 +0100 [thread overview]
Message-ID: <20201113080733.GZ2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201113020142.252688534@goodmis.org>
On Thu, Nov 12, 2020 at 09:01:42PM -0500, Steven Rostedt wrote:
> Steven Rostedt (VMware) (3):
> ftrace: Have the callbacks receive a struct ftrace_regs instead of pt_regs
> ftrace/x86: Allow for arguments to be passed in to ftrace_regs by default
> livepatch: Use the default ftrace_ops instead of REGS when ARGS is available
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2020-11-13 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 2:01 [PATCH 0/3 v6] ftrace: Add access to function arguments for all callbacks Steven Rostedt
2020-11-13 2:01 ` [PATCH 1/3 v6] ftrace: Have the callbacks receive a struct ftrace_regs instead of pt_regs Steven Rostedt
2020-11-13 2:01 ` [PATCH 2/3 v6] ftrace/x86: Allow for arguments to be passed in to ftrace_regs by default Steven Rostedt
2020-11-13 2:01 ` [PATCH 3/3 v6] livepatch: Use the default ftrace_ops instead of REGS when ARGS is available Steven Rostedt
2020-11-13 11:31 ` Miroslav Benes
2020-11-13 13:10 ` Steven Rostedt
2020-11-13 8:07 ` Peter Zijlstra [this message]
2020-11-13 13:26 ` [PATCH 0/3 v6] ftrace: Add access to function arguments for all callbacks 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=20201113080733.GZ2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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