[lkml]   [2009]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectFast testing

    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. Let's say you change some kernel
    source file and run "make" [this is fast since "make" should see that just few
    files are changed]. After "make install" you should now have new "vmlinux" file.
    Since state of cpu registers and memory locations determine current
    system state, the change in binary system driver ["vmlinux"] should not
    freeze system ? So if I copy new vmlinux over old vmlinux file can I see
    change immediately ? I think it should continue to drive system without
    problem because vmlinux is binary algorithm file, it does not contain any
    data regarding current system state ? Also this assumes that your change does
    not affect some large things, like memory segmentation tables and paging,
    let's say it is more algorithmic and not structure change, because it is obvious
    if you have structural change, current memory and register states
    probably won't map
    into new structure without system freeze.


    Dragoslav Zaric,

    [Programmer, M.Sc Astrophysics]

     \ /
      Last update: 2009-04-14 11:57    [W:0.021 / U:26.660 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site