From: devzero@web.de
To: linux-kernel@vger.kernel.org
Cc: dragoslav.zaric.kd@gmail.com
Subject: Re: Fast testing
Date: Wed, 15 Apr 2009 14:31:36 +0200 [thread overview]
Message-ID: <671763813@web.de> (raw)
if your kernel changes are not driver/hardware specific and you want to test/develop more
generic features, then you should have a look at UserModeLinux. great for testing & debugging.
you donŽt need any bootloader to run UserModeLinux, you can start it from commandline
just like any other process. Basically, it`s a Linux kernel ported to Linux API (instead of different ARCH)
regards
roland
List: linux-kernel
Subject: Re: Fast testing
From: Dragoslav Zaric <dragoslav.zaric.kd () gmail ! com>
Date: 2009-04-14 16:44:43
Message-ID: 2d05c4580904140944s1dec7dfewf42862ac698bf669 () mail ! gmail ! com
[Download message RAW]
Well Arjan it looks that you have a nice laptop if that is your
reboot time :)
The idea about this is that when you have some idea and you
write code, doing reboot and stuff can make you forgot your idea.
If you write normal program you probably press "build" or type
"gcc" at least 10 times to see what is going on. I think that only
thing necessary is: system to boot one time and then you can
load image in ram memory as many times as you want. So I am
not sure if this is ok, but at least I will try.
But I am not saying that if this works, the changes are going to
crush or freeze system more often than produce any kind of result :)
For example, we can boot from GRUB command line, so this would
be something like falling back to GRUB command line [to that point]
and load [any] image in ram memory.
thanks,
Dragoslav Zaric
__________________________________________________________________________
Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele
ausländische Netze zum gleichen Preis!
https://produkte.web.de/webde_sms/sms
next reply other threads:[~2009-04-15 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 12:31 devzero [this message]
2009-04-15 12:49 ` Fast testing Dragoslav Zaric
-- strict thread matches above, loose matches on Subject: below --
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-14 14:44 Tomasz Chmielewski
2009-04-14 9:55 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
2009-04-14 15:05 ` Arjan van de Ven
2009-04-14 16:44 ` Dragoslav Zaric
2009-04-15 11:48 ` Tilman Schmidt
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=671763813@web.de \
--to=devzero@web.de \
--cc=dragoslav.zaric.kd@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