netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, gospo@redhat.com,
	Greg Rose <gregory.v.rose@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next-2.6 PATCH 06/13] ixgbevf: Kconfig, Makefile and Documentation
Date: Sat, 09 Jan 2010 04:24:50 -0800	[thread overview]
Message-ID: <20100109122449.4462.16912.stgit@localhost.localdomain> (raw)
In-Reply-To: <20100109120719.4462.66489.stgit@localhost.localdomain>

From: Greg Rose <gregory.v.rose@intel.com>

Modifications for the Kconfig and network device Makefile to add the ixgbevf
driver module to the kernel plus basic driver documentation.

Signed-off-by: Greg Rose <gregory.v.rose@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---

 Documentation/networking/ixgbevf.txt |   90 ++++++++++++++++++++++++++++++++++
 drivers/net/Kconfig                  |   22 ++++++++
 drivers/net/Makefile                 |    1 
 3 files changed, 113 insertions(+), 0 deletions(-)
 create mode 100755 Documentation/networking/ixgbevf.txt

diff --git a/Documentation/networking/ixgbevf.txt b/Documentation/networking/ixgbevf.txt
new file mode 100755
index 0000000..19015de
--- /dev/null
+++ b/Documentation/networking/ixgbevf.txt
@@ -0,0 +1,90 @@
+Linux* Base Driver for Intel(R) Network Connection
+==================================================
+
+November 24, 2009
+
+Contents
+========
+
+- In This Release
+- Identifying Your Adapter
+- Known Issues/Troubleshooting
+- Support
+
+In This Release
+===============
+
+This file describes the ixgbevf Linux* Base Driver for Intel Network
+Connection.
+
+The ixgbevf driver supports 82599-based virtual function devices that can only
+be activated on kernels with CONFIG_PCI_IOV enabled.
+
+The ixgbevf driver supports virtual functions generated by the ixgbe driver
+with a max_vfs value of 1 or greater.
+
+The guest OS loading the ixgbevf driver must support MSI-X interrupts.
+
+VLANs: There is a limit of a total of 32 shared VLANs to 1 or more VFs.
+
+Identifying Your Adapter
+========================
+
+For more information on how to identify your adapter, go to the Adapter &
+Driver ID Guide at:
+
+    http://support.intel.com/support/network/sb/CS-008441.htm
+
+Known Issues/Troubleshooting
+============================
+
+  Unloading Physical Function (PF) Driver Causes System Reboots When VM is
+  Running and VF is Loaded on the VM
+  ------------------------------------------------------------------------
+  Do not unload the PF driver (ixgbe) while VFs are assigned to guests.
+
+Support
+=======
+
+For general information, go to the Intel support website at:
+
+    http://support.intel.com
+
+or the Intel Wired Networking project hosted by Sourceforge at:
+
+    http://sourceforge.net/projects/e1000
+
+If an issue is identified with the released source code on the supported
+kernel with a supported adapter, email the specific information related
+to the issue to e1000-devel@lists.sf.net
+
+License
+=======
+
+Intel 10 Gigabit Linux driver.
+Copyright(c) 1999 - 2009 Intel Corporation.
+
+This program is free software; you can redistribute it and/or modify it
+under the terms and conditions of the GNU General Public License,
+version 2, as published by the Free Software Foundation.
+
+This program is distributed in the hope it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
+more details.
+
+You should have received a copy of the GNU General Public License along with
+this program; if not, write to the Free Software Foundation, Inc.,
+51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
+
+The full GNU General Public License is included in this distribution in
+the file called "COPYING".
+
+Trademarks
+==========
+
+Intel, Itanium, and Pentium are trademarks or registered trademarks of
+Intel Corporation or its subsidiaries in the United States and other
+countries.
+
+* Other names and brands may be claimed as the property of others.
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index dd9a09c..5be6a23 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -2618,6 +2618,28 @@ config IXGBE_DCB
 
 	  If unsure, say N.
 
+config IXGBEVF
+       tristate "Intel(R) 82599 Virtual Function Ethernet support"
+       depends on PCI_MSI
+       ---help---
+         This driver supports Intel(R) 82599 virtual functions.  For more
+         information on how to identify your adapter, go to the Adapter &
+         Driver ID Guide at:
+
+         <http://support.intel.com/support/network/sb/CS-008441.htm>
+
+         For general information and support, go to the Intel support
+         website at:
+
+         <http://support.intel.com>
+
+         More specific information on configuring the driver is in
+         <file:Documentation/networking/ixgbevf.txt>.
+
+         To compile this driver as a module, choose M here. The module
+         will be called ixgbevf.  MSI-X interrupt support is required
+         for this driver to work correctly.
+
 config IXGB
 	tristate "Intel(R) PRO/10GbE support"
 	depends on PCI
diff --git a/drivers/net/Makefile b/drivers/net/Makefile
index ad1346d..6746e8b 100644
--- a/drivers/net/Makefile
+++ b/drivers/net/Makefile
@@ -14,6 +14,7 @@ obj-$(CONFIG_IBM_NEW_EMAC) += ibm_newemac/
 obj-$(CONFIG_IGB) += igb/
 obj-$(CONFIG_IGBVF) += igbvf/
 obj-$(CONFIG_IXGBE) += ixgbe/
+obj-$(CONFIG_IXGBEVF) += ixgbevf/
 obj-$(CONFIG_IXGB) += ixgb/
 obj-$(CONFIG_IP1000) += ipg.o
 obj-$(CONFIG_CHELSIO_T1) += chelsio/


  parent reply	other threads:[~2010-01-09 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 12:22 [net-next-2.6 PATCH 00/13] virtual function ixgbe driver Jeff Kirsher
2010-01-09 12:23 ` [net-next-2.6 PATCH 01/13] ixgbevf: Macros, data structures, useful defines and registers Jeff Kirsher
2010-01-09 12:23 ` [net-next-2.6 PATCH 02/13] ixgbevf: 82599 Virtual Function core functions and header Jeff Kirsher
2010-01-09 12:23 ` [net-next-2.6 PATCH 03/13] ixgbevf: Mailbox communication Jeff Kirsher
2010-01-09 12:24 ` [net-next-2.6 PATCH 04/13] ixgbevf: Driver main and ethool interface module and main header Jeff Kirsher
2010-01-09 12:24 ` [net-next-2.6 PATCH 05/13] ixgbevf: Driver Makefile Jeff Kirsher
2010-01-09 12:24 ` Jeff Kirsher [this message]
2010-01-09 12:25 ` [net-next-2.6 PATCH 07/13] ixgbe: Mailbox header and code module Jeff Kirsher
2010-01-09 12:25 ` [net-next-2.6 PATCH 08/13] ixgbe: Add SR-IOV register, structure and bit defines Jeff Kirsher
2010-01-09 12:25 ` [net-next-2.6 PATCH 09/13] ixgbe: Add SR-IOV specific features Jeff Kirsher
2010-01-09 12:26 ` [net-next-2.6 PATCH 10/13] ixgbe: Add SR-IOV specific modules to driver Makefile Jeff Kirsher
2010-01-09 12:26 ` [net-next-2.6 PATCH 11/13] ixgbe: Add SR-IOV feature enablement code Jeff Kirsher
2010-01-09 12:26 ` [net-next-2.6 PATCH 12/13] ixgbe: Add SR-IOV features to main module Jeff Kirsher
2010-01-09 12:27 ` [net-next-2.6 PATCH 13/13] ixgbe: Fix ethtool diag test for VT mode operation Jeff Kirsher
2010-01-10 21:35 ` [net-next-2.6 PATCH 00/13] virtual function ixgbe driver David Miller

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=20100109122449.4462.16912.stgit@localhost.localdomain \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=gregory.v.rose@intel.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).