Re: [PATCH 20/20] x86_64: Move CPU verification code to common file

> 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.

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

Follow-Ups:
- Re: [PATCH 20/20] x86_64: Move CPU verification code to common file
  - From: "H. Peter Anvin" <[email protected]>

References:
- [RFC][PATCH 0/20] x86_64: Relocatable bzImage (V3)
  - From: Vivek Goyal <[email protected]>
- [PATCH 20/20] x86_64: Move CPU verification code to common file
  - From: Vivek Goyal <[email protected]>
- Re: [PATCH 20/20] x86_64: Move CPU verification code to common file
  - From: Oleg Verych <[email protected]>

Prev by Date: Re: [RFC 6/7] Use an external declaration in exit.c for fs_cachep
Next by Date: Re: [RFC 6/7] Use an external declaration in exit.c for fs_cachep
Previous by thread: Re: [PATCH 20/20] x86_64: Move CPU verification code to common file
Next by thread: Re: [PATCH 20/20] x86_64: Move CPU verification code to common file
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]