linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Keith Busch <keith.busch@intel.com>,
	Bryan Veal <bryan.e.veal@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-pci@vger.kernel.org
Subject: [RFC PATCH 0/2] Driver for new PCI-e device
Date: Thu, 27 Aug 2015 16:39:04 -0600	[thread overview]
Message-ID: <1440715146-16578-1-git-send-email-keith.busch@intel.com> (raw)

The Intel Volume Management Device (VMD) is an integrated endpoint on the
platform's PCIe root complex that acts as a host bridge to a secondary
PCIe domain. BIOS can reassign one or more root ports to appear within
VMD domains instead of the primary domain. This driver enables and
enumerates the VMD domain using the root bus configuration interface
provided by the PCI subsystem.

CC: Bryan Veal <bryan.e.veal@intel.com>
CC: Dan Williams <dan.j.williams@intel.com>
CC: x86@kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-pci@vger.kernel.org

Keith Busch (2):
  x86: PCI bus specific MSI operations
  x86/pci: Initial commit for new VMD device driver

 arch/x86/Kconfig           |   11 ++
 arch/x86/include/asm/pci.h |    3 +
 arch/x86/kernel/x86_init.c |   19 ++
 arch/x86/pci/Makefile      |    2 +
 arch/x86/pci/vmd.c         |  412 ++++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 447 insertions(+)
 create mode 100644 arch/x86/pci/vmd.c

-- 
1.7.10.4


             reply	other threads:[~2015-08-27 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 22:39 Keith Busch [this message]
2015-08-27 22:39 ` [RFC PATCH 1/2] x86: PCI bus specific MSI operations Keith Busch
2015-08-28 16:54   ` Thomas Gleixner
2015-08-28 21:39     ` Keith Busch
2015-08-29  1:46     ` Jiang Liu
2015-08-27 22:39 ` [RFC PATCH 2/2] x86/pci: Initial commit for new VMD device driver Keith Busch

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=1440715146-16578-1-git-send-email-keith.busch@intel.com \
    --to=keith.busch@intel.com \
    --cc=bryan.e.veal@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=x86@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).