KXG60ZNV256G not recognized

[hch@infradead.org (Christoph Hellwig)]

On Wed, Feb 13, 2019@02:22:53PM -0700, Keith Busch wrote:
> To the best of my knowledge, the hardware mode is working around a
> software limitation that doesn't apply to Linux.

More correctly it works around a business model limitation that allows
Intel to sell an "integrated" fake raid driver.  Even more importantly
it works around that business model limitation in a completely gross
way, unlike the vmd solution to the same problem in another intel
division, which at least allows to recover from that workaround.

> > As such, I don't think that disdaining the technology will get Intel to change it.
> > So I'm hoping we can constructively come up with something that works in the confines
> > of its existence to make it a better experience at least.
> 
> I assumed Chritoph's comment was directed toward said software that runs
> on the majority of the client PC market, leaving hardware vendors to
> think up "creative" work-arounds to its quirks to the detriment of other
> software environments. :(

It affects everyone but Intel, that is vendors of non-Intel NVMe SSDs
that have no control on what windows driver is used for their devices,
and it includes any OS that does not have an Intel driver that knows
how to deal with the magic intel AHCI device, which is entirely Intel
private.

Even with the patches from Dan we can't properly use the NVMe device:

 - there is no support for MSI/MSI-X and thus no support for per-queue
   interrupts, thus severly limiting performance
 - there is no support for PCI ID based quirks, which we require
   to support various devices properly
 - there is no way to make SR-IOV work
 - there is no way to make PCI-level FLRs work, or to unbind the
   device in case of a fatal failure

All in all Intel is using their domniance of the CPU and shipset
business to harm various other parties.