From: Andi Kleen <ak@suse.de>
To: carl wolff <testkernel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Testing 2.6 kernel
Date: 03 Aug 2003 16:16:33 +0200 [thread overview]
Message-ID: <p73r842omgu.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20030803135745.64460.qmail@web20705.mail.yahoo.com.suse.lists.linux.kernel>
carl wolff <testkernel@yahoo.com> writes:
> Hello
>
> I've machinetime and machine (dell 530 Dual Xeon 1.4
> Ghz, 1GB) available to do automated kernel testing
> (2.6) based on LTP.
>
> Can anyone give answer to the following questions:
> 1) Is this helpful?
There are already various people testing LTP. It would
be better if you could test what you would normally do
(e.g. data base loads or whatever) because the "real world
coverage" is a bit more lacking.
> 2) Some small hints to get it very effective?
If you want to test LTP better concentrate less on
the standard functional runs, but more on the stress tests
to test your particular drivers etc. Often they have
to be invoked manually.
-Andi
next parent reply other threads:[~2003-08-03 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030803135745.64460.qmail@web20705.mail.yahoo.com.suse.lists.linux.kernel>
2003-08-03 14:16 ` Andi Kleen [this message]
2003-08-03 13:57 carl wolff
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=p73r842omgu.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=testkernel@yahoo.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 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®