linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/6] powerpc: add support for KPROBES_ON_FTRACE
Date: Wed, 19 Apr 2017 18:22:22 +0530	[thread overview]
Message-ID: <cover.1492605029.git.naveen.n.rao@linux.vnet.ibm.com> (raw)

v3:
https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg116800.html

For v4, patch 5/6 is new and has been moved into this series. It has
also been updated to use strlcat() instead of strncat(). No other
changes.

Also, though patch 3/6 is generic, it needs to be carried in this
series as we crash on powerpc without that patch.


- Naveen


Masami Hiramatsu (1):
  kprobes: Skip preparing optprobe if the probe is ftrace-based

Naveen N. Rao (5):
  powerpc: ftrace: minor cleanup
  powerpc: ftrace: restore LR from pt_regs
  powerpc: kprobes: add support for KPROBES_ON_FTRACE
  powerpc: introduce a new helper to obtain function entry points
  powerpc: kprobes: prefer ftrace when probing function entry

 .../debug/kprobes-on-ftrace/arch-support.txt       |   2 +-
 arch/powerpc/Kconfig                               |   1 +
 arch/powerpc/include/asm/code-patching.h           |  37 ++++++++
 arch/powerpc/include/asm/kprobes.h                 |  10 ++
 arch/powerpc/kernel/Makefile                       |   3 +
 arch/powerpc/kernel/entry_64.S                     |  19 ++--
 arch/powerpc/kernel/kprobes-ftrace.c               | 104 +++++++++++++++++++++
 arch/powerpc/kernel/kprobes.c                      |  25 ++++-
 arch/powerpc/kernel/optprobes.c                    |   6 +-
 kernel/kprobes.c                                   |  11 ++-
 10 files changed, 199 insertions(+), 19 deletions(-)
 create mode 100644 arch/powerpc/kernel/kprobes-ftrace.c

-- 
2.12.1

             reply	other threads:[~2017-04-19 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 12:52 Naveen N. Rao [this message]
     [not found] ` <cover.1492606062.git.naveen.n.rao@linux.vnet.ibm.com>
2017-04-19 12:52   ` [PATCH v4 1/6] powerpc: ftrace: minor cleanup Naveen N. Rao
2017-04-23 11:53     ` [v4,1/6] " Michael Ellerman
2017-04-19 12:52   ` [PATCH v4 2/6] powerpc: ftrace: restore LR from pt_regs Naveen N. Rao
2017-04-24 22:47     ` [v4,2/6] " Michael Ellerman
2017-04-19 12:52   ` [PATCH v4 3/6] kprobes: Skip preparing optprobe if the probe is ftrace-based Naveen N. Rao
2017-04-24 22:47     ` [v4, " Michael Ellerman
2017-04-19 12:52   ` [PATCH v4 4/6] powerpc: kprobes: add support for KPROBES_ON_FTRACE Naveen N. Rao
2017-04-24 22:47     ` [v4,4/6] " Michael Ellerman
2017-04-19 12:52   ` [PATCH v4 5/6] powerpc: introduce a new helper to obtain function entry points Naveen N. Rao
2017-04-24 22:47     ` [v4, " Michael Ellerman
2017-04-19 12:52   ` [PATCH v4 6/6] powerpc: kprobes: prefer ftrace when probing function entry Naveen N. Rao
2017-04-24 22:47     ` [v4, " Michael Ellerman

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=cover.1492605029.git.naveen.n.rao@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).