[lkml]   [2007]   [Dec]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/3 -mm] kexec jump -v8
    On Wed, 2007-12-26 at 20:57 -0500, Vivek Goyal wrote:
    > > 9. Now, you are in the original kernel again. You can read/write the
    > > memory image of kexeced kernel via /proc/kimgcore.
    > >
    > Why do we need two interfaces, /proc/vmcore and /proc/kimgcore? Can't
    > we have just one say /proc/vmcore. Irrespective of what kernel you are
    > in /proc/vmcore gives you the access to the memory of kernel which was
    > previously booted.

    In theory we can kexec another kernel even in a kexeced kernel, that is,
    in kernel A kexec kernel B, and in kernel B kexec another kernel C. In
    this situation, both /proc/vmcore and /proc/kimgcore has valid contents.
    So I think, it may be better to keep two interfaces.

    In fact, current kexec jump implementation use a dummy "jump back helper
    image" in kexeced kernel to jump back to the original kernel. The "jump
    back helper image" has no PT_LOAD segment, it is used to provide a
    struct kimage (including control page, swap page) and entry point to
    jump back.

    Best Regards,
    Huang Ying

     \ /
      Last update: 2007-12-27 03:35    [W:0.021 / U:79.396 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site