From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.redhat.com ([66.187.237.31]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1Kz7GZ-0003IH-Bs for kexec@lists.infradead.org; Sun, 09 Nov 2008 10:11:36 +0000 Message-ID: <4916B737.7050107@redhat.com> Date: Sun, 09 Nov 2008 12:11:03 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [PATCH 15/15] Revert "x86: default to reboot via ACPI" References: <1225915018-6548-1-git-send-email-ehabkost@redhat.com> <20081106143021.GD13023@elte.hu> <20081106150610.GA1644@elte.hu> <200811061853.08003.arvidjaar@mail.ru> <20081106215011.GA6391@srcf.ucam.org> <1226019679.3989.107.camel@yakui_zhao.sh.intel.com> <20081107005946.GA9254@srcf.ucam.org> In-Reply-To: <20081107005946.GA9254@srcf.ucam.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Matthew Garrett Cc: Andrew Morton , "Rafael J. Wysocki" , Eduardo Habkost , "kvm@vger.kernel.org" , "kexec@lists.infradead.org" , Linux Kernel Mailing List , Zhao Yakui , "linux-acpi@vger.kernel.org" , "Eric W. Biederman" , Ingo Molnar , Andrey Borzenkov , Len Brown 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 _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 15/15] Revert "x86: default to reboot via ACPI" Date: Sun, 09 Nov 2008 12:11:03 +0200 Message-ID: <4916B737.7050107@redhat.com> References: <1225915018-6548-1-git-send-email-ehabkost@redhat.com> <20081106143021.GD13023@elte.hu> <20081106150610.GA1644@elte.hu> <200811061853.08003.arvidjaar@mail.ru> <20081106215011.GA6391@srcf.ucam.org> <1226019679.3989.107.camel@yakui_zhao.sh.intel.com> <20081107005946.GA9254@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20081107005946.GA9254-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kexec-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Matthew Garrett Cc: Andrew Morton , "Rafael J. Wysocki" , Eduardo Habkost , "kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Linux Kernel Mailing List , Zhao Yakui , "linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "Eric W. Biederman" , Ingo Molnar , Andrey Borzenkov , Len Brown List-Id: linux-acpi@vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754795AbYKIKMw (ORCPT ); Sun, 9 Nov 2008 05:12:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753689AbYKIKMl (ORCPT ); Sun, 9 Nov 2008 05:12:41 -0500 Received: from mx2.redhat.com ([66.187.237.31]:41890 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751584AbYKIKMk (ORCPT ); Sun, 9 Nov 2008 05:12:40 -0500 Message-ID: <4916B737.7050107@redhat.com> Date: Sun, 09 Nov 2008 12:11:03 +0200 From: Avi Kivity User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Matthew Garrett CC: Zhao Yakui , Len Brown , Andrey Borzenkov , Ingo Molnar , Eduardo Habkost , "Eric W. Biederman" , Andrew Morton , "Rafael J. Wysocki" , "kexec@lists.infradead.org" , "kvm@vger.kernel.org" , Linux Kernel Mailing List , "linux-acpi@vger.kernel.org" Subject: Re: [PATCH 15/15] Revert "x86: default to reboot via ACPI" References: <1225915018-6548-1-git-send-email-ehabkost@redhat.com> <20081106143021.GD13023@elte.hu> <20081106150610.GA1644@elte.hu> <200811061853.08003.arvidjaar@mail.ru> <20081106215011.GA6391@srcf.ucam.org> <1226019679.3989.107.camel@yakui_zhao.sh.intel.com> <20081107005946.GA9254@srcf.ucam.org> In-Reply-To: <20081107005946.GA9254@srcf.ucam.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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