mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: the Linux kernel, testsuites, and maybe *you*
Date: Sat, 1 Sep 2007 18:50:30 -0400	[thread overview]
Message-ID: <8bd0f97a0709011550y833fb5ax7d40cae937789fd8@mail.gmail.com> (raw)
In-Reply-To: <p733axyxcli.fsf@bingen.suse.de>

On 02 Sep 2007 00:08:57 +0200, Andi Kleen <andi@firstfloor.org> wrote:
> BTW string functions are best tested in user space. That's
> a relatively bad example.

in theory, maybe ... in reality, i really dont think so

the string implementations are spread out over the kernel ... there's
implementations in lib/, include/asm-*/, and arch/*/lib/ ... so any
test code that would use these sources is going to be an ugly hack to
make sure it grabs all the right pieces from all the right places.

then there's the issue of API ... compiling code that is designed to
be in the kernel and nowhere else is going to require a mighty bit of
crappy glue logic in order for it to compile properly in userspace

but let's cheat and just use the kernel build system to produce .o's
for us ... then there's the issue of ABI.  there is no guarantee the
ABI the kernel uses internally is the same as the ABI userspace uses
(and in fact, on some architectures it is simply not possible).  so
you're left with a solution that may work for some, but not for
others.

or we put one common piece of C test code right into the kernel and be
done.  no worrying about the tested API/ABI/environment being
different from the actual runtime the kernel itself has.
-mike

  reply	other threads:[~2007-09-01 22:50 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
2007-09-01 22:08 ` Andi Kleen
2007-09-01 22:50   ` Mike Frysinger [this message]
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=8bd0f97a0709011550y833fb5ax7d40cae937789fd8@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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®