lkml.org 
[lkml]   [2006]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH] x86_64 kexec: Remove experimental mark of kexec
    Date
    Piet Delaney <piet@bluelane.com> writes:

    > On Wed, 2006-09-06 at 14:15 -0600, Eric W. Biederman wrote:
    >> Andi Kleen <ak@suse.de> writes:
    >>
    >> > On Wednesday 06 September 2006 18:55, Eric W. Biederman wrote:
    >> >>
    >> >> kexec has been marked experimental for a year now and all
    >> >> of the serious problems have been worked through. So it
    >> >> is time (if not past time) to remove the experimental mark.
    >> >>
    >> >
    >> > Hmm, I personally have some doubts it is really not experimental
    >> > (not because of the kexec code itself, but because of all the other drivers
    >> > that still break)
    >>
    >> That is a reasonable viewpoint. Although by that a lot more of the kernel
    >> deserves to be marked experimental.
    >>
    >> On the perverse side of the sentiment taking off experimental may increase
    >> our number of testers and get the bugs fixed faster :)
    >
    > I take it that for using kexec to boot a kdump kernel and then
    > rebooting the primary kernel that there are a few drivers in
    > the dumping kernel that wouldn't work but they aren't likely
    > to be used. Ie: it's "just" a hardware initialization issue
    > on kernels booted with kexec.

    Yes. The only place you are likely to observe the driver
    initialization problems are kernels booted with kexec. But there
    are other rare scenarios that can yield challenging boot driver
    initialization scenarios. I know soft booting from windows used
    to be one of them.

    As for the kdump kernel usually you won't load (or build in) any
    drivers you don't intend to use. If the drivers actually get loaded
    even if you aren't using them you could have problems.

    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: 2006-09-07 08:59    [W:8.300 / U:0.196 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site