[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080910224130.GC16740@ldl.fc.hp.com>
Date: Wed, 10 Sep 2008 16:41:30 -0600
From: Alex Chiang <achiang@...com>
To: "Zhao, Yu" <yu.zhao@...el.com>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>, linux-pci@...r.kernel.org,
Randy Dunlap <randy.dunlap@...cle.com>,
Greg KH <greg@...ah.com>,
Grant Grundler <grundler@...isc-linux.org>,
Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
xen-devel@...ts.xensource.com
Subject: Re: [PATCH 3/4 v2] PCI: support SR-IOV capability
* Zhao, Yu <yu.zhao@...el.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
--
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