Skip to contentSkip to conversation

Fast testing

DISCUSSION [email protected] 2 participants 2 messages Apr 15, 2009

lore
Share & tools
lore
#0 lore 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

#1 lore raw

Well the idea wasn't about what is faster, rebooting or loading kernel image in ram memory, it was about loading kernel image in ram to see and debug things. And if you reboot there is time delay and the point is why doing it, if you can just smash another kernel image in ram memory and drive.

I mean, this does not make sense in production environment use, it is for debugging.

Anyway, the simplest first try is to get somehow at grub command line and load kernel image in ram and hope this works :) If not, then write small program is the only solution.

The only concern is can you burn your laptop with assembly instructions ?? :)

thanks,

Dragoslav Zaric

[Programmer; M. Sc Astrophysics]