[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b2b86520904140636x1971b44g898c29e8b0904396@mail.gmail.com>
Date: Tue, 14 Apr 2009 14:36:46 +0100
From: Alan Jenkins <sourcejedi.lkml@...glemail.com>
To: Dragoslav Zaric <dragoslav.zaric.kd@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Cyrill Gorcunov <gorcunov@...il.com>
Subject: Re: Fast testing
On 4/14/09, Dragoslav Zaric <dragoslav.zaric.kd@...il.com> wrote:
> Hello,
>
> I have question regarding fast testing of some change in some kernel
> source file. Since rebooting is a long process, there must be way to
> test some change faster [of course only if source file is not some boot
> connected file, but maybe this is also doable].
>
> This is question:
>
> When system is running, file that drives the system is "vmlinux" executable
> and it is located in "/" or "/boot" folder.
Nope.
Kernel code (and data) is not demand-paged. The kernel image is fully
loaded into memory at boot-time. Changing /boot/vmlinuz will have no
effect on the running kernel. And there are several other reasons why
what you describe would not work.
What you can do is compile some code as a module, and remove and
re-insert it to apply changes. This doesn't work for core code or
your main disk driver though :-).
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists