From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
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: Re: [PATCH v2 0/5] powerpc: a few kprobe fixes and refactoring
Date: Thu, 13 Apr 2017 12:02:17 +0900 [thread overview]
Message-ID: <20170413120217.0a1223bdaea42448ec011c66@kernel.org> (raw)
In-Reply-To: <cover.1491991939.git.naveen.n.rao@linux.vnet.ibm.com>
Hi Naveen,
BTW, I saw you sent 3 different series, are there any
conflict each other? or can we pick those independently?
Thanks,
On Wed, 12 Apr 2017 16:28:23 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> v1:
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1334843.html
>
> For v2, this series has been re-ordered and rebased on top of
> powerpc/next so as to make it easier to resolve conflicts with -tip. No
> other changes.
>
> - Naveen
>
>
> Naveen N. Rao (5):
> kprobes: convert kprobe_lookup_name() to a function
> powerpc: kprobes: fix handling of function offsets on ABIv2
> powerpc: introduce a new helper to obtain function entry points
> powerpc: kprobes: factor out code to emulate instruction into a helper
> powerpc: kprobes: emulate instructions on kprobe handler re-entry
>
> arch/powerpc/include/asm/code-patching.h | 37 ++++++++++
> arch/powerpc/include/asm/kprobes.h | 53 --------------
> arch/powerpc/kernel/kprobes.c | 119 +++++++++++++++++++++++++------
> arch/powerpc/kernel/optprobes.c | 6 +-
> include/linux/kprobes.h | 1 +
> kernel/kprobes.c | 21 +++---
> 6 files changed, 147 insertions(+), 90 deletions(-)
>
> --
> 2.12.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-04-13 3:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 10:58 [PATCH v2 0/5] powerpc: a few kprobe fixes and refactoring Naveen N. Rao
2017-04-12 10:58 ` [PATCH v2 1/5] kprobes: convert kprobe_lookup_name() to a function Naveen N. Rao
2017-04-13 3:09 ` Masami Hiramatsu
2017-04-18 12:52 ` David Laight
2017-04-19 8:08 ` Naveen N. Rao
2017-04-19 8:48 ` David Laight
2017-04-19 11:07 ` 'Naveen N. Rao'
2017-04-12 10:58 ` [PATCH v2 2/5] powerpc: kprobes: fix handling of function offsets on ABIv2 Naveen N. Rao
2017-04-13 4:28 ` Masami Hiramatsu
2017-04-12 10:58 ` [PATCH v2 3/5] powerpc: introduce a new helper to obtain function entry points Naveen N. Rao
2017-04-13 4:32 ` Masami Hiramatsu
2017-04-13 5:52 ` Naveen N. Rao
2017-04-12 10:58 ` [PATCH v2 4/5] powerpc: kprobes: factor out code to emulate instruction into a helper Naveen N. Rao
2017-04-13 4:34 ` Masami Hiramatsu
2017-04-13 5:53 ` Naveen N. Rao
2017-04-13 8:50 ` Naveen N. Rao
2017-04-12 10:58 ` [PATCH v2 5/5] powerpc: kprobes: emulate instructions on kprobe handler re-entry Naveen N. Rao
2017-04-13 4:37 ` Masami Hiramatsu
2017-04-13 5:53 ` Naveen N. Rao
2017-04-13 3:02 ` Masami Hiramatsu [this message]
2017-04-13 5:50 ` [PATCH v2 0/5] powerpc: a few kprobe fixes and refactoring Naveen N. Rao
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=20170413120217.0a1223bdaea42448ec011c66@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).