[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080103110459.GI29194@elte.hu>
Date: Thu, 3 Jan 2008 12:04:59 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Ananth N Mavinakayanahalli <ananth@...ibm.com>
Cc: akpm@...ux-foundation.org, lkml <linux-kernel@...r.kernel.org>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
davem@...emloft.net, mathieu.desnoyers@...ymtl.ca,
hskinnemoen@...el.com, mhiramat@...hat.com, sam@...nborg.org,
randy.dunlap@...cle.com
Subject: Re: [PATCH 2/2] Kprobes: Move kprobes examples to samples/
* Ananth N Mavinakayanahalli <ananth@...ibm.com> wrote:
> > feature request: please make this work in the !modular case as well
> > - if built-in then it should just run sometime during bootup and run
> > the tests and report success/failure. This way automated testing can
> > pick up any regressions much easier.
>
> Will try cook up something along those lines. It'll be easy to verify
> if the probes inserted and removed properly, but verifying handlers
> run correctly will need some work.
>
> We have a sort of regression test bucket that uses expect to parse the
> dmesg to verify handlers did run correctly; that isn't a totally
> in-kernel solution anyway. I have a couple of ideas in mind to make it
> easier.
Great. Would be really nice to have something along the lines of
CONFIG_DEBUG_LOCKING_API_SELFTESTS. Those unit tests took time to
develop, but they caught more than 90% (!) of the internal lockdep
engine bugs before they ever hit mainline.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists