[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4916B737.7050107@redhat.com>
Date:	Sun, 09 Nov 2008 12:11:03 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Matthew Garrett <mjg@...hat.com>
CC:	Zhao Yakui <yakui.zhao@...el.com>, Len Brown <lenb@...nel.org>,
	Andrey Borzenkov <arvidjaar@...l.ru>,
	Ingo Molnar <mingo@...e.hu>,
	Eduardo Habkost <ehabkost@...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"
Matthew Garrett wrote:
> 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.
>   
Isn't it the other way around?  The firmware changes behavior depending 
on how the OS identifies itself?
Reboot is a fixed feature IIRC, so it cannot change depending on 
identification strings.
-- 
error compiling committee.c: too many arguments to function
--
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
 
