public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
	tglx@linutronix.de, jpoimboe@redhat.com, x86@kernel.org,
	mhiramat@kernel.org, mbenes@suse.cz, jthierry@redhat.com,
	alexandre.chartre@oracle.com
Subject: [PATCH 0/3] x86/ftrace: Make created trampolines not call direct code
Date: Wed, 22 Apr 2020 12:25:39 -0400	[thread overview]
Message-ID: <20200422162539.808362933@goodmis.org> (raw)

Peter,

These three patches are built on top of your patch series.

This is what I was thinking of having. This isn't fully tested
(as your patch series is still running on my test suite).

-- Steve


Steven Rostedt (VMware) (3):
      x86/ftrace: Make non direct case the default in ftrace_regs_caller
      x86/ftrace: Only have the builtin ftrace_regs_caller call direct hooks
      x86/ftrace: Do not jump to direct code in created trampolines

----
 arch/x86/kernel/ftrace.c    | 14 +++++++++++---
 arch/x86/kernel/ftrace_64.S | 29 ++++++++++++++---------------
 kernel/trace/ftrace.c       |  8 ++++++++
 3 files changed, 33 insertions(+), 18 deletions(-)

             reply	other threads:[~2020-04-22 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 16:25 Steven Rostedt [this message]
2020-04-22 16:25 ` [PATCH 1/3] x86/ftrace: Make non direct case the default in ftrace_regs_caller Steven Rostedt
2020-04-22 16:25 ` [PATCH 2/3] x86/ftrace: Only have the builtin ftrace_regs_caller call direct hooks Steven Rostedt
2020-04-22 16:25 ` [PATCH 3/3] x86/ftrace: Do not jump to direct code in created trampolines Steven Rostedt
2020-04-22 20:08   ` Peter Zijlstra
2020-04-22 20:17     ` 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=20200422162539.808362933@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=alexandre.chartre@oracle.com \
    --cc=jpoimboe@redhat.com \
    --cc=jthierry@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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