[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081107005946.GA9254@srcf.ucam.org>
Date: Fri, 7 Nov 2008 00:59:46 +0000
From: Matthew Garrett <mjg@...hat.com>
To: Zhao Yakui <yakui.zhao@...el.com>
Cc: Len Brown <lenb@...nel.org>, Andrey Borzenkov <arvidjaar@...l.ru>,
Ingo Molnar <mingo@...e.hu>,
Eduardo Habkost <ehabkost@...hat.com>,
Avi Kivity <avi@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...l.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH 15/15] Revert "x86: default to reboot via ACPI"
On Fri, Nov 07, 2008 at 09:01:19AM +0800, Zhao Yakui wrote:
> With the help of KVM I find that the windows will be rebooted by writing
> RESET_VALUE to RESET_REG I/O port if the RESET_REG_SUP bit is not
> zero(It indicates whether ACPI reboot is supported).
> IMO maybe the ACPI reboot is the first choice. If it can't, then it will
> fall back to other mode.
Hmm. But we're seeing some machines that end up very confused if
rebooted via ACPI. I guess we need to run Vista on them to find out how
they behave. What OSI strings did your KVM setup expose? We know that
Windows changes behaviour under various circumstances depending on which
OS the firmware requests, so it's almost possible that this is another
of those cases.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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