From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:47336)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1RxHoy-00053P-Mi
	for qemu-devel@nongnu.org; Tue, 14 Feb 2012 07:49:30 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1RxHop-0000jj-6N
	for qemu-devel@nongnu.org; Tue, 14 Feb 2012 07:49:24 -0500
Received: from relay1.mentorg.com ([192.94.38.131]:45217)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1RxHop-0000jd-1o
	for qemu-devel@nongnu.org; Tue, 14 Feb 2012 07:49:15 -0500
From: Paul Brook <paul@codesourcery.com>
Date: Tue, 14 Feb 2012 12:49:08 +0000
References: <cover.1329124507.git.mst@redhat.com>
	<20120214004837.GA14752@morn.localdomain>
	<20120214010913.GA5192@redhat.com>
In-Reply-To: <20120214010913.GA5192@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201202141249.09301.paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH RFC] seabios: add OSHP method stub
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, seabios@seabios.org, Isaku Yamahata <yamahata@valinux.co.jp>, Kevin O'Connor <kevin@koconnor.net>, Avi Kivity <avi@redhat.com>

> > In a nutshell, I don't know what a SHPC is (nor OSHP), so I'm looking
> > for an additional Ack.
> 
> No problem, I'll get an Ack :)
> Meanwhile - here's a summary, as far as I understand it.
> 
> Originally PCI SIG only defined the electrical
> and mechanical requirements from hotplug, no standard
> software interface. So it needed ACPI to drive device-specific registers
> to actually do hotplug.
> At some point PCISIG defined standard interfaces
> for PCI hotplug. There are two of them: standard
> hot plug controller (SHPC) for PCI and PCIE hotplug
> for Express.
> 
> 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?

Paul