From: Matthew Wilcox <matthew@wil.cx>
To: Yu Zhao <yu.zhao@intel.com>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 1/8] PCI: initialize and release SR-IOV capability
Date: Thu, 19 Mar 2009 13:53:12 -0600 [thread overview]
Message-ID: <20090319195312.GC14127@parisc-linux.org> (raw)
In-Reply-To: <1236756349-18892-2-git-send-email-yu.zhao@intel.com>
On Wed, Mar 11, 2009 at 03:25:42PM +0800, Yu Zhao wrote:
> +config PCI_IOV
> + bool "PCI IOV support"
> + depends on PCI
> + help
> + PCI-SIG I/O Virtualization (IOV) Specifications support.
> + Single Root IOV: allows the creation of virtual PCI devices
> + that share the physical resources from a real device.
> +
> + When in doubt, say N.
It's certainly shorter than my text, which is nice. But I think it
still has too much spec-ese and not enough explanation. How about:
help
I/O Virtualization is a PCI feature supported by some devices
which allows them to create virtual devices which share their
physical resources.
If unsure, say N.
> + list_for_each_entry(pdev, &dev->bus->devices, bus_list)
> + if (pdev->is_physfn)
> + break;
> + if (list_empty(&dev->bus->devices) || !pdev->is_physfn)
> + pdev = NULL;
This is still wrong. If the 'break' condition is not hit, pdev is
pointing to garbage, not to the last pci_dev in the list.
> @@ -270,6 +278,7 @@ struct pci_dev {
> struct list_head msi_list;
> #endif
> struct pci_vpd *vpd;
> + struct pci_sriov *sriov; /* SR-IOV capability related */
Should be ifdeffed?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-19 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 7:25 [PATCH v11 0/8] PCI: Linux kernel SR-IOV support Yu Zhao
2009-03-11 7:25 ` [PATCH v11 1/8] PCI: initialize and release SR-IOV capability Yu Zhao
2009-03-19 19:53 ` Matthew Wilcox [this message]
2009-03-20 1:20 ` Jesse Barnes
2009-03-20 1:42 ` Matthew Wilcox
2009-03-20 3:28 ` Zhao, Yu
2009-03-20 2:06 ` Yu Zhao
2009-03-11 7:25 ` [PATCH v11 2/8] PCI: restore saved SR-IOV state Yu Zhao
2009-03-11 7:25 ` [PATCH v11 3/8] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-03-11 7:25 ` [PATCH v11 4/8] PCI: centralize device setup code Yu Zhao
2009-03-11 7:25 ` [PATCH v11 5/8] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-03-11 7:25 ` [PATCH v11 6/8] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-03-11 7:25 ` [PATCH v11 7/8] PCI: document SR-IOV sysfs entries Yu Zhao
2009-03-11 7:25 ` [PATCH v11 8/8] PCI: manual for SR-IOV user and driver developer Yu Zhao
2009-03-17 1:55 ` [PATCH v11 0/8] PCI: Linux kernel SR-IOV support 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=20090319195312.GC14127@parisc-linux.org \
--to=matthew@wil.cx \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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.