From: Ingo Molnar <mingo@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-pci@vger.kernel.org,
Jiang Liu <jiang.liu@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dan Williams <dan.j.williams@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Bryan Veal <bryan.e.veal@intel.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC PATCHv2] x86/pci: Initial commit for new VMD device driver
Date: Sat, 3 Oct 2015 11:45:12 +0200 [thread overview]
Message-ID: <20151003094512.GA29104@gmail.com> (raw)
In-Reply-To: <1443721454-25467-1-git-send-email-keith.busch@intel.com>
* Keith Busch <keith.busch@intel.com> wrote:
> +config VMDDEV
> + depends on PCI && PCI_DOMAINS && PCI_MSI && GENERIC_MSI_IRQ_DOMAIN && IRQ_DOMAIN_HIERARCHY
> + tristate "Volume Management Device Driver"
> + default N
> + select HAVE_VMDDEV
> + ---help---
> + Adds support for the Intel Volume Manage Device (VMD). VMD is
> + a secondary PCI host bridge that allows PCI Express root ports,
> + and devices attached to them, to be removed from the default PCI
> + domain and placed within the VMD domain. If your system provides
> + one of these and has devices attached to it, say "Y".
So what this text does not explain is why does the user care? What tangible
benefits does this feature offer to users?
Thanks,
Ingo
next prev parent reply other threads:[~2015-10-03 9:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 17:44 [RFC PATCHv2] x86/pci: Initial commit for new VMD device driver Keith Busch
2015-10-03 9:45 ` Ingo Molnar [this message]
2015-10-05 14:34 ` Keith Busch
2015-10-05 16:46 ` Ingo Molnar
2015-10-05 18:03 ` Keith Busch
2015-10-04 0:29 ` kbuild test robot
2015-10-06 23:14 ` Bjorn Helgaas
2015-10-07 0:21 ` Keith Busch
2015-10-07 16:04 ` Keith Busch
2015-10-08 13:29 ` Bjorn Helgaas
2015-10-08 13:47 ` Bjorn Helgaas
2015-10-08 21:33 ` Keith Busch
2015-10-09 18:09 ` Bjorn Helgaas
2015-10-09 19:22 ` Keith Busch
2015-10-13 9:57 ` Martin Mares
2015-10-12 21:05 ` 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=20151003094512.GA29104@gmail.com \
--to=mingo@kernel.org \
--cc=bhelgaas@google.com \
--cc=bryan.e.veal@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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).