From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 0/5] ahci: nvme remap support
Date: Sat, 22 Oct 2016 08:50:38 +0200 [thread overview]
Message-ID: <20161022065038.GA8547@lst.de> (raw)
In-Reply-To: <147709592108.3733.7194541797066785254.stgit@dwillia2-desk3.amr.corp.intel.com>
On Fri, Oct 21, 2016@05:25:21PM -0700, Dan Williams wrote:
> Some Intel ahci implementations have the capability to expose another
> pci-express device's memory resources through an ahci memory bar. Add
> the enabling to detect these configurations and register the resources
> for the nvme driver to consume. Otherwise, the nvme device is
> effectively hidden from the kernel for this configuration.
Honestly I think this is just too ugly to live. I think people getting
tricked by Intel into buying this piece of junk will just have to live
with AHCI mode.
next prev parent reply other threads:[~2016-10-22 6:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 0:25 [PATCH 0/5] ahci: nvme remap support Dan Williams
2016-10-22 0:25 ` [PATCH 1/5] " Dan Williams
2016-10-22 0:25 ` [PATCH 2/5] nvme: rename "pci" operations to "mmio" Dan Williams
2016-10-22 0:25 ` [PATCH 3/5] nvme: introduce nvme_dev_ops Dan Williams
2016-10-22 0:25 ` [PATCH 4/5] nvme: move common definitions to pci.h Dan Williams
2016-10-22 0:25 ` [PATCH 5/5] nvme: ahci remap support Dan Williams
2016-10-22 6:50 ` Christoph Hellwig [this message]
2016-10-22 19:26 ` [PATCH 0/5] ahci: nvme " Dan Williams
2016-10-23 8:34 ` Christoph Hellwig
2016-10-23 13:57 ` Dan Williams
2016-10-24 12:49 ` Christoph Hellwig
2016-10-24 14:46 ` Keith Busch
2016-10-24 15:16 ` Christoph Hellwig
2016-10-24 17:46 ` Dan Williams
2016-10-24 17:55 ` Christoph Hellwig
2016-10-24 21:01 ` Dan Williams
2016-10-24 17:57 ` Dan Williams
2016-10-24 18:21 ` Christoph Hellwig
2016-11-15 18:52 ` Christoph Hellwig
2016-11-19 6:12 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161022065038.GA8547@lst.de \
--to=hch@lst.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).