From: David Long <dave.long@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Rabin Vincent <rabin@rab.in>,
"Jon Medhurst (Tixy)" <tixy@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 4/9] uprobes: allow arch-specific initialization
Date: Thu, 1 Aug 2013 19:45:48 -0400 [thread overview]
Message-ID: <1375400753-3454-5-git-send-email-dave.long@linaro.org> (raw)
In-Reply-To: <1375400753-3454-1-git-send-email-dave.long@linaro.org>
From: Rabin Vincent <rabin@rab.in>
Add a weak function for any architecture-specific initialization. ARM
will use this to register the handlers for the undefined instructions it
uses to implement uprobes.
Signed-off-by: Rabin Vincent <rabin@rab.in>
Signed-off-by: David A. Long <dave.long@linaro.org>
---
include/linux/uprobes.h | 1 +
kernel/events/uprobes.c | 10 ++++++++++
2 files changed, 11 insertions(+)
diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
index f6287f0..6feae5d 100644
--- a/include/linux/uprobes.h
+++ b/include/linux/uprobes.h
@@ -135,6 +135,7 @@ extern int arch_uprobe_exception_notify(struct notifier_block *self, unsigned l
extern void arch_uprobe_abort_xol(struct arch_uprobe *aup, struct pt_regs *regs);
extern bool __weak arch_uprobe_ignore(struct arch_uprobe *aup, struct pt_regs *regs);
extern void __weak arch_uprobe_xol_copy(struct arch_uprobe *auprobe, void *vaddr);
+extern int __weak arch_uprobes_init(void);
#else /* !CONFIG_UPROBES */
struct uprobes_state {
};
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index 64471bd..5004f6f 100644
--- a/kernel/events/uprobes.c
+++ b/kernel/events/uprobes.c
@@ -1862,8 +1862,14 @@ static struct notifier_block uprobe_exception_nb = {
.priority = INT_MAX-1, /* notified after kprobes, kgdb */
};
+int __weak __init arch_uprobes_init(void)
+{
+ return 0;
+}
+
static int __init init_uprobes(void)
{
+ int ret;
int i;
for (i = 0; i < UPROBES_HASH_SZ; i++)
@@ -1872,6 +1878,10 @@ static int __init init_uprobes(void)
if (percpu_init_rwsem(&dup_mmap_sem))
return -ENOMEM;
+ ret = arch_uprobes_init();
+ if (ret)
+ return ret;
+
return register_die_notifier(&uprobe_exception_nb);
}
module_init(init_uprobes);
--
1.8.1.2
next prev parent reply other threads:[~2013-08-01 23:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 23:45 [PATCH 0/9] uprobes: Add uprobes support for ARM David Long
2013-08-01 23:45 ` [PATCH 1/9] uprobes: move function declarations out of arch David Long
2013-08-01 23:45 ` [PATCH 2/9] uprobes: allow ignoring of probe hits David Long
2013-08-01 23:45 ` [PATCH 3/9] uprobes: allow arch access to xol slot David Long
2013-08-01 23:45 ` David Long [this message]
2013-08-01 23:45 ` [PATCH 5/9] uprobes: add arch write opcode hook David Long
2013-08-01 23:45 ` [PATCH 6/9] ARM: move shared uprobe/kprobe definitions into new include file David Long
2013-08-01 23:45 ` [PATCH 7/9] ARM: Move uprobes/kprobes shared functions to common file David Long
2013-08-29 14:08 ` Jon Medhurst (Tixy)
2013-08-01 23:45 ` [PATCH 8/9] ARM: Add "action" table for kprobes/uprobes instruction David Long
2013-08-29 14:09 ` Jon Medhurst (Tixy)
2013-08-01 23:45 ` [PATCH 9/9] ARM: add uprobes support David Long
2013-08-29 14:54 ` Jon Medhurst (Tixy)
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=1375400753-3454-5-git-send-email-dave.long@linaro.org \
--to=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
--cc=tixy@linaro.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;
as well as URLs for NNTP newsgroup(s).