From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH] x86: default to reboot via ACPI Date: Tue, 26 Aug 2008 13:07:15 +0200 Message-ID: <20080826110715.GA26204@elte.hu> References: <1219659087-17536-1-git-send-email-avi@qumranet.com> <20080826095032.GA309@elf.ucw.cz> <48B3D579.40502@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , Pavel Machek , "Eric W. Biederman" , linux-kernel@vger.kernel.org, kvm@vger.kernel.org To: Frans Meulenbroeks Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:48203 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753231AbYHZLH3 (ORCPT ); Tue, 26 Aug 2008 07:07:29 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: * Frans Meulenbroeks wrote: > 2008/8/26 Avi Kivity : > > > It seems excessive. Most machines will hardly run without acpi. > > Well, I'm fairly sure that most of the systems running linux (or some > variant like uclinux), do not support acpi. > > Linux is used a lot in embedded systems (like routers and NAS-es and > probably set-top boxes). I guess the # of embedded systems with some > linux flavour on it is substantially bigger than the desktop systems. > Most of these are ARM or MIPS based and do not support ACPI. ... which is not an issue in this particular discussion, which was about x86 with ACPI support enabled and available, whether in that case (and only in that case) we should first try the ACPI reboot ports (that the ACPI descriptors advertise) before also trying the other methods (kdb, bios, triple fault, etc.) to reboot the box. Ingo