From: hch@infradead.org (Christoph Hellwig)
Subject: AHCI NVMe remap update
Date: Tue, 17 Oct 2017 23:30:27 -0700 [thread overview]
Message-ID: <20171018063027.GA12755@infradead.org> (raw)
In-Reply-To: <CAD8Lp450TSnpzTAGiAgKjJws6VnVu9ZWv_x-GFQ5RhNOTnNCpQ@mail.gmail.com>
On Wed, Oct 18, 2017@11:01:33AM +0800, Daniel Drake wrote:
> Would be great if you could take another look at this.
The right way to do this would be to expose a fake PCIe root port
that both the AHCI and NVMe driver bind to. But only Intel has the
detailed information to do this. Especially as we'd have to do
things like recovering the exact PCI ID for quirks in the NVMe driver
to make this whole scheme work reliably.
prev parent reply other threads:[~2017-10-18 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 3:01 AHCI NVMe remap update Daniel Drake
2017-10-18 6:30 ` Christoph Hellwig [this message]
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=20171018063027.GA12755@infradead.org \
--to=hch@infradead.org \
/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).