From: Alex Chiang <achiang@hp.com>
To: "Zhao, Yu" <yu.zhao@intel.com>
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
Subject: Re: [PATCH 3/4 v2] PCI: support SR-IOV capability
Date: Wed, 10 Sep 2008 16:41:30 -0600 [thread overview]
Message-ID: <20080910224130.GC16740@ldl.fc.hp.com> (raw)
In-Reply-To: <7A25B56E4BE99C4283EB931CD1A40E110181CB1A@pdsmsx414.ccr.corp.intel.com>
* 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
prev parent reply other threads:[~2008-09-10 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 11:21 [PATCH 3/4 v2] PCI: support SR-IOV capability Zhao, Yu
2008-09-01 15:30 ` Alex Chiang
2008-09-10 7:36 ` Zhao, Yu
2008-09-01 16:41 ` Alex Chiang
2008-09-10 7:59 ` Zhao, Yu
2008-09-10 22:41 ` Alex Chiang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080910224130.GC16740@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=randy.dunlap@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
--cc=yu.zhao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox