From: Ingo Molnar <mingo@elte.hu>
To: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: akpm@linux-foundation.org, lkml <linux-kernel@vger.kernel.org>,
Jim Keniston <jkenisto@us.ibm.com>,
mhiramat@redhat.com, davem@davemloft.net, hskinnemoen@atmel.com
Subject: Re: [PATCH] Kprobes: Add kprobes smoke tests that run on boot
Date: Tue, 8 Jan 2008 10:15:50 +0100 [thread overview]
Message-ID: <20080108091550.GC27671@elte.hu> (raw)
In-Reply-To: <20080108063334.GA29385@in.ibm.com>
* Ananth N Mavinakayanahalli <ananth@in.ibm.com> wrote:
> From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
>
> Here is a quick and naive smoke test for kprobes. This is intended to
> just verify if some unrelated change broke the *probes subsystem. It
> is self contained, architecture agnostic and isn't of any great use by
> itself.
>
> This needs to be built in the kernel and runs a basic set of tests to
> verify if kprobes, jprobes and kretprobes run fine on the kernel. In
> case of an error, it'll print out a message with a "BUG" prefix.
yay! Picked this up into x86.git for testing.
small detail: i moved the kernel/Makefile change to another spot (see
below), this way it integrates without rejects with rcu-preempt and with
the kgdb changes.
Ingo
Index: linux-x86.q/kernel/Makefile
===================================================================
--- linux-x86.q.orig/kernel/Makefile
+++ linux-x86.q/kernel/Makefile
@@ -43,6 +43,7 @@ obj-$(CONFIG_CPUSETS) += cpuset.o
obj-$(CONFIG_CGROUP_NS) += ns_cgroup.o
obj-$(CONFIG_IKCONFIG) += configs.o
obj-$(CONFIG_STOP_MACHINE) += stop_machine.o
+obj-$(CONFIG_KPROBES_SANITY_TEST) += test_kprobes.o
obj-$(CONFIG_AUDIT) += audit.o auditfilter.o
obj-$(CONFIG_AUDITSYSCALL) += auditsc.o
obj-$(CONFIG_AUDIT_TREE) += audit_tree.o
next prev parent reply other threads:[~2008-01-08 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 6:33 [PATCH] Kprobes: Add kprobes smoke tests that run on boot Ananth N Mavinakayanahalli
2008-01-08 9:15 ` Ingo Molnar [this message]
2008-01-08 21:00 ` Andi Kleen
2008-01-08 22:18 ` Ingo Molnar
2008-01-08 22:49 ` Andi Kleen
2008-01-08 22:50 ` Ingo Molnar
2008-01-09 8:00 ` Christoph Hellwig
2008-01-09 8:08 ` Sam Ravnborg
2008-01-08 23:10 ` Jim Keniston
2008-01-08 23:28 ` Andi Kleen
2008-01-09 20:24 ` Jim Keniston
2008-01-09 21:21 ` Andi Kleen
2008-01-09 22:33 ` Jim Keniston
2008-01-09 7:43 ` David Miller
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=20080108091550.GC27671@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=hskinnemoen@atmel.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.