From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Chiang <achiang@hp.com>
Subject: Re: [PATCH 3/4 v2] PCI: support SR-IOV capability
Date: Wed, 10 Sep 2008 16:41:30 -0600
Message-ID: <20080910224130.GC16740@ldl.fc.hp.com>
References: <7A25B56E4BE99C4283EB931CD1A40E110177EB6F@pdsmsx414.ccr.corp.intel.com> <20080901164104.GG16796@ldl.fc.hp.com> <7A25B56E4BE99C4283EB931CD1A40E110181CB1A@pdsmsx414.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>, linux-pci@vger.kernel.org,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Greg KH <greg@kroah.com>,
	Grant Grundler <grundler@parisc-linux.org>,
	Matthew Wilcox <matthew@wil.cx>, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com
To: "Zhao, Yu" <yu.zhao@intel.com>
Return-path: <linux-pci-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <7A25B56E4BE99C4283EB931CD1A40E110181CB1A@pdsmsx414.ccr.corp.intel.com>
Sender: linux-pci-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

* Zhao, Yu <yu.zhao@intel.com>:
> On Tuesday, September 02, 2008 12:41 AM, Alex Chiang wrote:
> >
> >So, what happens if another hotplug driver is already loaded?
> >
> >I don't know the SR-IOV spec well enough to know if you are
> >allowed to have SR-IOV + some other form of hotplug, like ACPI or
> >native PCIe.
> >
> >Today, pci_hp_register will return -EBUSY.
> >
> >If SR-IOV really doesn't have anything to do with hotplug, then
> >it may be a candidate for directly calling pci_create_slot(). In
> >that case, 'param' should not be a property of a hotplug slot,
> >but of a generic PCI slot.
> 
> That's correct, SR-IOV really doesn't have anything to do with
> hotplug. I was just reusing hotplug sysfs as the control
> interface. Will remove this in next work, and create SR-IOV own
> sysfs entries under /sys/bus/pci/devices/.../iov/...

That sounds like a much better idea to me, thanks.

/ac