Messages in this thread | | | Date | Mon, 5 Oct 2015 18:46:24 +0200 | From | Ingo Molnar <> | Subject | Re: [RFC PATCHv2] x86/pci: Initial commit for new VMD device driver |
| |
* Keith Busch <keith.busch@intel.com> wrote:
> On Sat, 3 Oct 2015, Ingo Molnar wrote: > >* 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? > > Hi Ingo, > > The immediate benefit is that devices on VMD domains do not use resources > on the default PCI domain, so we have more than the 256 buses available.
Would be nice to incorporate that information in the help text and in the changelog.
Thanks,
Ingo
| |