Re: [PATCH] x86_64 kexec: Remove experimental mark of kexec

[Piet Delaney <piet@bluelane.com>]

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.

-piet

> 
> > But applied for now.
> 
> Thanks.
> 
> 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/
-- 
Piet Delaney                                    Phone: (408) 200-5256
Blue Lane Technologies                          Fax:   (408) 200-5299
10450 Bubb Rd.
Cupertino, Ca. 95014                            Email: piet@bluelane.com

Attachment: signature.asc
Description: This is a digitally signed message part