[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <455EAB28.9000500@zytor.com>
Date: Fri, 17 Nov 2006 22:41:44 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Andi Kleen <ak@...e.de>
CC: LKML <linux-kernel@...r.kernel.org>, olecom@...wer.upol.cz,
vgoyal@...ibm.com, akpm@...l.org, rjw@...k.pl,
ebiederm@...ssion.com, Reloc Kernel List <fastboot@...ts.osdl.org>,
pavel@...e.cz, magnus.damm@...il.com
Subject: Re: [PATCH 20/20] x86_64: Move CPU verification code to common file
Andi Kleen wrote:
>> May hang be done optional? There was a discussion about applying
>> "panic" reboot timeout here. Is it possible to implement somehow?
>
> It would be tricky, but might be possible. But that would be a completely
> new feature -- the kernel has always hung in this case. If you think you need
> it submit a (followup) patch. But I don't think it's fair to ask Vivek to do it.
>
> Besides i don't think it would be any useful. panic reboot only
> makes sense if you can recover after reboot. But if your CPU somehow
> suddenly loses its ability to run 64bit code, no reboot of the world will
> recover.
>
Not true. Some bootloaders support a fallback kernel. This case is
particular important if one accidentally installs the wrong kernel for
the machine.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists