* Keith Busch <keith.busch@xxxxxxxxx> wrote: > On Sat, 3 Oct 2015, Ingo Molnar wrote: > >* Keith Busch <keith.busch@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
