From: Randy Dunlap <rdunlap@xenotime.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Yu Zhao <yu.zhao@intel.com>,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 1/7] PCI: initialize and release SR-IOV capability
Date: Fri, 06 Mar 2009 14:03:33 -0800 [thread overview]
Message-ID: <49B19DB5.9050606@xenotime.net> (raw)
In-Reply-To: <20090306200810.GD25995@parisc-linux.org>
Matthew Wilcox wrote:
> On Fri, Feb 20, 2009 at 02:54:42PM +0800, Yu Zhao wrote:
>> +config PCI_IOV
>> + bool "PCI IOV support"
>> + depends on PCI
>> + select PCI_MSI
>
> My understanding is that having 'select' of a config symbol that the
> user can choose is bad. I think we should probably make this 'depends
> on PCI_MSI'.
Ack.
> PCI MSI can also be disabled at runtime (and Fedora do by default).
> Since SR-IOV really does require MSI, we need to put in a runtime check
> to see if pci_msi_enabled() is false.
>
> We don't depend on PCIEPORTBUS (a horribly named symbol). Should we?
> SR-IOV is only supported for PCI Express machines. I'm not sure of the
> right answer here, but I thought I should raise the question.
>
>> + help
>> + PCI-SIG I/O Virtualization (IOV) Specifications support.
>> + Single Root IOV: allows the Physical Function driver to enable
>> + the hardware capability, so the Virtual Function is accessible
>> + via the PCI Configuration Space using its own Bus, Device and
>> + Function Numbers. Each Virtual Function also has the PCI Memory
>> + Space to map the device specific register set.
Too spec. and implementation specific for users.
> I'm not convinced this is the most helpful we could be to the user who's
> configuring their own kernel. How about something like this? (Randy, I
> particularly look to you to make my prose less turgid).
>
> help
> IO Virtualisation is a PCI feature supported by some devices
z ;)
> which allows you to create virtual PCI devices and assign them
> to guest OSes. This option needs to be selected in the host
> or Dom0 kernel, but does not need to be selected in the guest
> or DomU kernel. If you don't know whether your hardware supports
> it, you can check by using lspci to look for the SR-IOV capability.
>
> If you have no idea what any of that means, it is safe to
> answer 'N' here.
That's certainly more readable and user-friendly.
I don't know what else it needs. Looks good to me.
~Randy
next prev parent reply other threads:[~2009-03-06 22:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:54 [PATCH v10 0/7] PCI: Linux kernel SR-IOV support Yu Zhao
2009-02-20 6:54 ` [PATCH v10 1/7] PCI: initialize and release SR-IOV capability Yu Zhao
2009-03-06 20:08 ` Matthew Wilcox
2009-03-06 22:03 ` Randy Dunlap [this message]
2009-03-06 23:31 ` Duyck, Alexander H
2009-03-07 2:38 ` Greg KH
2009-03-10 1:19 ` Yu Zhao
2009-03-11 4:36 ` Greg KH
2009-03-09 8:12 ` Yu Zhao
2009-02-20 6:54 ` [PATCH v10 2/7] PCI: restore saved SR-IOV state Yu Zhao
2009-03-06 20:09 ` Matthew Wilcox
2009-02-20 6:54 ` [PATCH v10 3/7] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-03-06 20:20 ` Matthew Wilcox
2009-03-09 8:13 ` Yu Zhao
2009-03-09 18:09 ` Randy Dunlap
2009-03-09 18:11 ` Matthew Wilcox
2009-02-20 6:54 ` [PATCH v10 4/7] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-03-06 20:37 ` Matthew Wilcox
2009-03-06 21:48 ` Randy Dunlap
2009-03-09 8:29 ` Yu Zhao
2009-03-07 2:40 ` Greg KH
2009-03-09 8:25 ` Yu Zhao
2009-03-09 19:39 ` Greg KH
2009-03-10 1:37 ` Yu Zhao
2009-03-11 4:34 ` Greg KH
2009-02-20 6:54 ` [PATCH v10 5/7] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-03-06 21:13 ` Matthew Wilcox
2009-03-09 8:28 ` Yu Zhao
2009-02-20 6:54 ` [PATCH v10 6/7] PCI: document SR-IOV sysfs entries Yu Zhao
2009-03-06 21:16 ` Matthew Wilcox
2009-03-06 22:35 ` Randy Dunlap
2009-02-20 6:54 ` [PATCH v10 7/7] PCI: manual for SR-IOV user and driver developer Yu Zhao
2009-03-06 21:17 ` Matthew Wilcox
2009-02-24 10:47 ` [PATCH v10 0/7] PCI: Linux kernel SR-IOV support Avi Kivity
2009-02-25 1:36 ` Yu Zhao
2009-03-06 19:33 ` Matthew Wilcox
2009-03-08 14:30 ` Avi Kivity
2009-03-08 15:01 ` Matthew Wilcox
2009-03-09 0:45 ` Greg KH
2009-03-09 3:42 ` Yang, Sheng
2009-03-09 4:35 ` Yang, Sheng
2009-03-09 13:45 ` Avi Kivity
2009-03-06 19:44 ` Matthew Wilcox
2009-03-07 2:34 ` Greg KH
2009-03-10 1:11 ` Yu Zhao
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=49B19DB5.9050606@xenotime.net \
--to=rdunlap@xenotime.net \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.