From: Himanshu Chauhan <hschauhan@nulltrace.org>
To: linux-kernel@vger.kernel.org
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: [PATCH][UPDATED] MIPS: Kprobe support v0.2
Date: Sat, 12 Jun 2010 21:50:55 +0530 [thread overview]
Message-ID: <1276359656-2375-1-git-send-email-hschauhan@nulltrace.org> (raw)
In-Reply-To: <1276359441-1846-1-git-send-email-hschauhan@nulltrace.org>
This updated version of patch incorporates some of the comments
from Daney. The list of changes are as follows:
o Instead of separate handler "do_break", do_bp is used to
track and handle kprobe induced breaks. This cleans up ugly
ifdef hack.
o Instead of using 0 and 5 code in break, new kprobe specific
defines (515, 516) have been added and handled.
The use of notify_die could not be dropped because the kprobes
framework installs handlers on notify_die chain.
Himanshu Chauhan (1):
MIPS: Kprobe support v0.2 This incorporates some of the comments
from Daney.
arch/mips/Kconfig | 13 ++
arch/mips/include/asm/break.h | 2 +
arch/mips/include/asm/kdebug.h | 5 +
arch/mips/include/asm/kprobes.h | 86 +++++++++
arch/mips/kernel/Makefile | 2 +
arch/mips/kernel/kprobes.c | 379 +++++++++++++++++++++++++++++++++++++++
arch/mips/kernel/traps.c | 46 +++++-
arch/mips/mm/fault.c | 11 +-
8 files changed, 541 insertions(+), 3 deletions(-)
create mode 100644 arch/mips/include/asm/kprobes.h
create mode 100644 arch/mips/kernel/kprobes.c
next parent reply other threads:[~2010-06-12 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276359441-1846-1-git-send-email-hschauhan@nulltrace.org>
2010-06-12 16:20 ` Himanshu Chauhan [this message]
2010-06-12 16:20 ` [PATCH] MIPS: Kprobe support v0.2 This incorporates some of the comments from Daney Himanshu Chauhan
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=1276359656-2375-1-git-send-email-hschauhan@nulltrace.org \
--to=hschauhan@nulltrace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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
Powered by JetHome