All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Zhao <yu.zhao@intel.com>
To: jbarnes@virtuousgeek.org
Cc: linux-pci@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Yu Zhao <yu.zhao@intel.com>
Subject: [PATCH v8 0/7] PCI: Linux kernel SR-IOV support
Date: Tue, 10 Feb 2009 16:59:08 +0800	[thread overview]
Message-ID: <1234256355-23153-1-git-send-email-yu.zhao@intel.com> (raw)

Greetings,

Following patches are intended to support SR-IOV capability in the
Linux kernel. With these patches, people can turn a PCI device with
the capability into multiple ones from software perspective, which
will benefit KVM and achieve other purposes such as QoS, security,
and etc.

SR-IOV specification can be found at:
http://www.pcisig.com/members/downloads/specifications/iov/sr-iov1.0_11Sep07.pdf
(it requires membership.)

Devices that support SR-IOV are available from following vendors:
http://download.intel.com/design/network/ProdBrf/320025.pdf
http://www.neterion.com/products/x3100.html

Physical Function driver for Intel 82576 NIC (based on drivers/net/igb/)
will come in few weeks.

Major changes from v7 to v8:
1, simplified the API for the PF driver
2, split the code and respin them against the latest tree

Yu Zhao (7):
  PCI: initialize and release SR-IOV capability
  PCI: restore saved SR-IOV state
  PCI: reserve bus range for SR-IOV device
  PCI: add SR-IOV API for Physical Function driver
  PCI: handle SR-IOV Virtual Function Migration
  PCI: document SR-IOV sysfs entries
  PCI: manual for SR-IOV user and driver developer

 Documentation/ABI/testing/sysfs-bus-pci |   27 ++
 Documentation/DocBook/kernel-api.tmpl   |    1 +
 Documentation/PCI/pci-iov-howto.txt     |  106 +++++
 drivers/pci/Kconfig                     |   13 +
 drivers/pci/Makefile                    |    3 +
 drivers/pci/iov.c                       |  692 +++++++++++++++++++++++++++++++
 drivers/pci/pci.c                       |    8 +
 drivers/pci/pci.h                       |   53 +++
 drivers/pci/probe.c                     |    7 +
 include/linux/pci.h                     |   28 ++
 include/linux/pci_regs.h                |   33 ++
 11 files changed, 971 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/PCI/pci-iov-howto.txt
 create mode 100644 drivers/pci/iov.c


             reply	other threads:[~2009-02-10  9:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  8:59 Yu Zhao [this message]
2009-02-10  8:59 ` [PATCH v8 1/7] PCI: initialize and release SR-IOV capability Yu Zhao
2009-02-13 16:56   ` Andi Kleen
2009-02-13 12:30     ` Yu Zhao
2009-02-13 17:49     ` Matthew Wilcox
2009-02-13 12:47       ` Yu Zhao
2009-02-10  8:59 ` [PATCH v8 2/7] PCI: restore saved SR-IOV state Yu Zhao
2009-02-10  8:59 ` [PATCH v8 3/7] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-02-10  8:59 ` [PATCH v8 4/7] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-02-10  8:59 ` [PATCH v8 5/7] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-02-10  8:59 ` [PATCH v8 6/7] PCI: document SR-IOV sysfs entries Yu Zhao
2009-02-10  8:59 ` [PATCH v8 7/7] PCI: manual for SR-IOV user and driver developer 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=1234256355-23153-1-git-send-email-yu.zhao@intel.com \
    --to=yu.zhao@intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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.