From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RxJ77-0002vZ-Op for qemu-devel@nongnu.org; Tue, 14 Feb 2012 09:12:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RxJ6y-00005a-8h for qemu-devel@nongnu.org; Tue, 14 Feb 2012 09:12:13 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RxJ6y-00005J-18 for qemu-devel@nongnu.org; Tue, 14 Feb 2012 09:12:04 -0500 Date: Tue, 14 Feb 2012 16:11:57 +0200 From: "Michael S. Tsirkin" Message-ID: <20120214141157.GA24489@redhat.com> References: <201202141249.09301.paul@codesourcery.com> <20120214133727.GA23647@redhat.com> <201202141348.00060.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201202141348.00060.paul@codesourcery.com> Subject: Re: [Qemu-devel] [PATCH RFC] seabios: add OSHP method stub List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Kevin Wolf , kvm@vger.kernel.org, seabios@seabios.org, qemu-devel@nongnu.org, Isaku Yamahata , Kevin O'Connor , Avi Kivity On Tue, Feb 14, 2012 at 01:47:59PM +0000, Paul Brook wrote: > > > > Now an OS can have a standard driver and use it > > > > to activate hotplug functionality. This is OS hotplug (OSHP). > > > > > > So presumably this will work on targets that don't have ACPI? > > > Assuming a competent guest OS of course. Have you tested this? > > > > This being the qemu side of things? I run Linux > > and verified that it calls OSHP and afterwards, > > runs the native driver and handles hotplug/unplug > > without invoking ACPI at all. > > I mean using your shiny new hotplug PCI-PCI bridge on arm/ppc/mips targets > (i.e anything other than x86 PC). From your description it sounds like it > *should* work. > > > It seems that at least the SHPC driver in linux > > doesn't work if you don't have an acpi table > > with the OSHP method - not many people run with acpi=off > > nowdays, so it's probably just a bug. > > I'll check how hard it is to fix this. > > Targets other than x86 don't have ACPI to start with. > > Paul So #ifdef CONFIG_ACPI #include static inline int get_hp_hw_control_from_firmware(struct pci_dev *dev) { u32 flags = OSC_SHPC_NATIVE_HP_CONTROL; return acpi_get_hp_hw_control_from_firmware(dev, flags); } #else #define get_hp_hw_control_from_firmware(dev) (0) #endif So if you build your guest without acpi, things should work fine. -- MMST