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

From: H. Peter Anvin
Date: Sat Nov 18 2006 - 02:33:47 EST


Oleg Verych wrote:
On Fri, Nov 17, 2006 at 10:59:32PM -0800, H. Peter Anvin wrote:
Oleg Verych wrote:
It will burn CPU, until power cycle will be done (my AMD64 laptop and
Intel's amd64 destop PC require that). In case of reboot timeout (or
just reboot with jump to BIOS), i will just choose another image to boot
or will press F8 to have another boot device.

That's a fairly stupid argument, since it assumes operator intervention, at which point you have access to the machine anyway.

I would never call *power cycle* stupid, just because from physics
point of veiw.

Example. I have my flower.upol.cz many kilometers far away from me.
I used to boot it from that flash (new hardware, sata problems, etc).

When something goes wrong with rc kernel or power source, bum.
And i had to move my ass there, just to press reset. Because.

Yes, and you would have to do that to press F8 too.

While i have "power on, on AC failures" in BIOS, *sometimes* flash
will not boot (i don't know why, maybe it's GRUB+flash-read,
or BIOS usb hdd implementation specific).

I was making the point that there is unattended recovery possible. That makes it a significant argument. That a user on a laptop has to wait four seconds pushing the power button is not.

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