lkml.org 
[lkml]   [2002]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Kexec for v2.5.47-bk2
    From
    Date
    Suparna Bhattacharya <suparna@in.ibm.com> writes:

    > On Wed, Nov 13, 2002 at 06:26:29AM -0700, Eric W. Biederman wrote:
    > >
    > > O.k. and now a version that applies cleanly to
    > > v2.5.47-bk2 aka ChangeSet@1.845
    > >
    >
    > BTW, results similar to Andy on my SMP system (the same problem
    > machine we'd talked about earlier). Same problem ?

    Something like that. The good news is that the image is being
    loaded the bad news is the BIOS doesn't work, and so the kernels
    initial setup code isn't working.

    Hopefully this weekend I can do the work in user space to bypass
    the BIOS altogether for booting a kernel. That should make the whole
    thing easier to use.

    > with 2.5.47-bk2
    > + kexec patch for 2.5.47-bk2 attached in your mail
    > + linux-2.5.47.x86kexec-hwfixes
    > and using
    > kexec-tools-1.5
    >
    > Results of kexec kexec_test
    >
    > [root@llm01 root]# Synchronizing SCSI caches:
    > Shutting down devices
    > Starting new kernel
    > kexec_test 1.5 starting...
    > eax: 0E1FB007 ebx: 00001078 ecx: 00000000 edx: 00000000
    > esi: 00000000 edi: 00000000 esp: 00000000 ebp: 00000000
    > idt: 00000000 C0000000
    > gdt: 00000000 C0000000
    > Switching descriptors.
    > Descriptors changed.
    > Legacy pic setup.
    > In real mode.
    > <hang>
    >
    > What would be best way to pass a parameter or address from the
    > current kernel to kernel being booted (e.g log buffer address
    > or crash dump buffer etc) ? Should this be part of the interface,
    > i.e. could/would it make sense for kexec to support this (rather
    > than our having to go and try to fix up kernel parameters ourselves,
    > or designate a fixed address for this) ? Also thinking
    > about other arch support for kexec in the future ...

    The current interface says load image X at location Y, and entry
    at point Z. Given that every little situation wants a slightly
    different tweak I don't think a specific feature in the kernel is
    needed. The user space binaries can incorporate all of the
    interesting logic.

    Eric
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:31    [W:4.180 / U:0.100 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site