From: Andi Kleen <andi@firstfloor.org>
To: Dragoslav Zaric <dragoslav.zaric.kd@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: Fast testing
Date: Tue, 14 Apr 2009 15:53:20 +0200 [thread overview]
Message-ID: <87vdp7735b.fsf@basil.nowhere.org> (raw)
In-Reply-To: <2d05c4580904140255t25414b2bpe99b2a150dbe132a@mail.gmail.com> (Dragoslav Zaric's message of "Tue, 14 Apr 2009 11:55:10 +0200")
Dragoslav Zaric <dragoslav.zaric.kd@gmail.com> writes:
As others pointed out vmlinux is not demand paged.
> Since rebooting is a long process,
The trick is to not make it a long process. Some ways to do that:
- Test simple changes in emulation. Emulators tend to boot faster
than real systems.
- Use a stripped down Linux distribution that boots fast. I found
that just using a old Linux distribution (without udev with static /dev)
and minimal services boots dramatically faster. I use opensuse 10.0 for that.
- When you need to test on a real system use nfsroot with kernel
boot through PXE. First that saves you one iteration of rebooting/copying
to update a kernel. And then the NFS server can keep the small nfsroot cached
in memory and then deliver it immediately.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-14 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 9:55 Fast testing Dragoslav Zaric
2009-04-14 13:36 ` Alan Jenkins
2009-04-14 14:10 ` Dragoslav Zaric
2009-04-14 14:24 ` Dragoslav Zaric
2009-04-14 14:57 ` Cyrill Gorcunov
2009-04-14 13:53 ` Andi Kleen [this message]
2009-04-14 15:05 ` Arjan van de Ven
2009-04-14 16:44 ` Dragoslav Zaric
2009-04-15 11:48 ` Tilman Schmidt
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 14:44 Tomasz Chmielewski
2009-04-15 12:19 Tomasz Chmielewski
2009-04-15 12:45 ` Tilman Schmidt
2009-04-16 0:47 ` Robert Hancock
2009-04-16 15:19 ` Valdis.Kletnieks
2009-04-15 12:31 devzero
2009-04-15 12:49 ` Dragoslav Zaric
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=87vdp7735b.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=dragoslav.zaric.kd@gmail.com \
--cc=gorcunov@gmail.com \
--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