Re: [PATCHv8 0/5] Driver for new "VMD" device

From	"Veal, Bryan E." <bryan.e.veal@intel.com>
Newsgroups	linux.kernel
Subject	Re: [PATCHv8 0/5] Driver for new "VMD" device
Date	2016-01-19 23:10 +0100
Message-ID	<qSMDo-5wa-23@gated-at.bofh.it> (permalink)
References	(2 earlier) <qRixI-2cl-27@gated-at.bofh.it> <qRkJd-3M8-41@gated-at.bofh.it> <qSGxY-1lu-33@gated-at.bofh.it> <qSH10-1Nb-9@gated-at.bofh.it> <qSHu2-1ZJ-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Jan 19, 2016 at 04:36:36PM +0000, Keith Busch wrote:
> On Tue, Jan 19, 2016 at 08:02:20AM -0800, Christoph Hellwig wrote:
> > As this seems to require special drivers to bind to it, and Intel
> > people refuse to even publicly tell what the code does I'd like
> > to NAK this code until we get an explanation and use cases for it.
> 
> We haven't opened the h/w specification, but we've been pretty open with
> what it provides, how the code works, and our intended use case. The
> device provides additional pci domains for people who need more than
> the 256 busses a single domain provides.
> 
> What information may I provide to satisfy your use case concerns? Are
> you wanting to know what devices we have in mind that require additional
> domains?

VMD is simply a convenient way to create a new PCIe host bridge that
happens to sit on the existing PCIe root bus. It changes how I/O is
routed (i.e. BDF translation), but not its contents. We've actually gone
through some effort in the code *avoid* special drivers by implementing
the existing host bridge abstractions. The cases where existing drivers
wouldn't work are due to limitations, not arbitrary filters. (For
example, it doesn't know how to route legacy IO ports or INTx.)

Thread

Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <helgaas@kernel.org> - 2016-01-15 19:20 +0100
  Re: [PATCHv8 0/5] Driver for new "VMD" device "Veal, Bryan E." <bryan.e.veal@intel.com> - 2016-01-15 20:40 +0100
    Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <helgaas@kernel.org> - 2016-01-15 22:50 +0100
      Re: [PATCHv8 0/5] Driver for new "VMD" device "Veal, Bryan E." <bryan.e.veal@intel.com> - 2016-01-16 23:30 +0100
        Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <helgaas@kernel.org> - 2016-01-20 23:30 +0100
  Re: [PATCHv8 0/5] Driver for new "VMD" device Keith Busch <keith.busch@intel.com> - 2016-01-15 20:40 +0100
  Re: [PATCHv8 0/5] Driver for new "VMD" device Thomas Gleixner <tglx@linutronix.de> - 2016-01-15 20:50 +0100
    Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <bhelgaas@google.com> - 2016-01-15 21:10 +0100
      Re: [PATCHv8 0/5] Driver for new "VMD" device Thomas Gleixner <tglx@linutronix.de> - 2016-01-15 21:20 +0100
  RE: [PATCHv8 0/5] Driver for new "VMD" device "Derrick, Jonathan" <jonathan.derrick@intel.com> - 2016-01-15 20:50 +0100
    Re: [PATCHv8 0/5] Driver for new "VMD" device Keith Busch <keith.busch@intel.com> - 2016-01-15 21:00 +0100
      Re: [PATCHv8 0/5] Driver for new "VMD" device Jon Derrick <jonathan.derrick@intel.com> - 2016-01-15 21:10 +0100
    Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <helgaas@kernel.org> - 2016-01-15 23:10 +0100
      Re: [PATCHv8 0/5] Driver for new "VMD" device Keith Busch <keith.busch@intel.com> - 2016-01-19 16:40 +0100
        Re: [PATCHv8 0/5] Driver for new "VMD" device Christoph Hellwig <hch@infradead.org> - 2016-01-19 17:10 +0100
          Re: [PATCHv8 0/5] Driver for new "VMD" device Keith Busch <keith.busch@intel.com> - 2016-01-19 17:40 +0100
            Re: [PATCHv8 0/5] Driver for new "VMD" device "Veal, Bryan E." <bryan.e.veal@intel.com> - 2016-01-19 23:10 +0100
          Re: [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas <helgaas@kernel.org> - 2016-01-20 21:50 +0100
            Re: [PATCHv8 0/5] Driver for new "VMD" device Christoph Hellwig <hch@infradead.org> - 2016-01-26 17:50 +0100
              Re: [PATCHv8 0/5] Driver for new "VMD" device "Veal, Bryan E." <bryan.e.veal@intel.com> - 2016-01-26 19:30 +0100

csiph-web