[Bug 233960] Add Volume Management Device (VMD) stub driver

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Dec 12 17:01:54 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233960

            Bug ID: 233960
           Summary: Add Volume Management Device (VMD) stub driver
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: dave.fugate at gmail.com

Created attachment 200058
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200058&action=edit
VMD Driver Patch

At a high-level, "Intel® VMD enables hot swap replacement of NVMe* SSDs from
the PCIe* bus without shutting down the system while standardized LED
management helps provide quick identification of SSD status."  

This is realized through the addition of a VMD controller on the PCIe bus of
high-end systems (e.g., Xeon) which "hides" 1 to N PCIe ports underneath it. 
As you might imagine, this implies the need for a VMD driver which either
delegates incoming NVMe requests to the appropriate drivers (e.g., NVMe,
hot-plug, etc.) or a VMD driver which incorporates the NVMe, hot-plug, etc.
functionality all on its own.

FreeBSD is missing either such type of VMD driver today, and consequently
end-users like Netflix are getting the mistaken impression FreeBSD doesn't have
a driver for their invisible NVMe devices or the NVMe devices are broken...

Attached to this bug report is a patch adding a VMD stub driver informing the
end-user they should disable the VMD feature in their BIOS.  This stub driver
is a stop-gap measure to eventually be replaced with a full-fledged VMD driver
(I work for the NVMe/VMD OSS driver team at Intel).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list