From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Robin Getz" <rgetz@blackfin.uclinux.org>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>, mbligh@mbligh.org
Subject: Re: the Linux kernel, testsuites, and maybe *you*
Date: Sat, 1 Sep 2007 18:52:39 -0400 [thread overview]
Message-ID: <8bd0f97a0709011552u687bcdc7i3a9154b24523796d@mail.gmail.com> (raw)
In-Reply-To: <200709010214.11128.rgetz@blackfin.uclinux.org>
On 9/1/07, Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> On Fri 31 Aug 2007 17:22, Mike Frysinger pondered:
> > is there any sort of standard for testing and integration into
> > mainline ? in the Blackfin world, we've been developing little
> > external kernel modules and adding them to our own testsuite, but
> > often times these things are not Blackfin specific. case in point,
> > we're integrating a string testsuite to make sure all of the fun str*
> > and mem* functions are sane and operate as they expected, but rather
> > than having just Blackfin benefit here, i'd like to see this pushed
> > upstream ...
>
> I know there have been some discussions at past OLS about some testing that
> Martin was working on.
>
> http://www.linuxsymposium.org/2006/view_abstract.php?content_key=13
>
> But I think this was more functional tests, less unit tests that what you are
> talking/asking about.
>
> http://test.kernel.org/functional/index.html
>
> Also - If I remember - most of the existing tests were for a self hosted
> environment - and might not be well suited to embedded (like Blackfin) which
> requires cross compile, and pretty thin runtime environment (uClibc +
> busybox's msh as shell).
i flipped through the autotest code a bit but i dont think this can do
what i'm looking for. it appears to be a mix of LTP provides and what
we have for our Blackfin test infrastructure -- iow, all userspace
stuff and no real way of exercising kernel internals.
-mike
next prev parent reply other threads:[~2007-09-01 22:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 21:22 Mike Frysinger
2007-09-01 6:14 ` Robin Getz
2007-09-01 22:52 ` Mike Frysinger [this message]
2007-09-01 22:08 ` Andi Kleen
2007-09-01 22:50 ` Mike Frysinger
2007-09-02 6:59 ` Andi Kleen
2007-09-02 15:15 ` Mike Frysinger
2007-09-02 15:43 ` Andi Kleen
2007-09-04 15:05 ` Mike Frysinger
2007-09-05 17:51 ` Mike Frysinger
2007-09-02 18:20 ` Håvard Skinnemoen
2007-09-04 14:41 ` Robin Getz
2007-09-02 2:34 ` Bill Davidsen
2007-09-02 3:44 ` Mike Frysinger
2007-09-03 13:37 ` Bill Davidsen
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=8bd0f97a0709011552u687bcdc7i3a9154b24523796d@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=rgetz@blackfin.uclinux.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
all inboxes | Powered by JetHome®