From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: tj@kernel.org, keith.busch@intel.com, linux-ide@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/5] ahci: nvme remap support
Date: Tue, 15 Nov 2016 19:52:07 +0100 [thread overview]
Message-ID: <20161115185207.GB5854@lst.de> (raw)
In-Reply-To: <147709592108.3733.7194541797066785254.stgit@dwillia2-desk3.amr.corp.intel.com>
As it's been a few weeks since this initial posting: What's the
status of either getting the magic chipset handshake mode published
to take the chipset out of this degraded mode, or implementing a bridge
driver like VMD?
It seems devices supporting this "slow down the devices and make life
hell for the OS" mode are getting more common, so we'll have to do
something about it.
next prev parent reply other threads:[~2016-11-15 18:52 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 ` [PATCH 0/5] ahci: nvme " Christoph Hellwig
2016-10-22 19:26 ` 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 [this message]
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=20161115185207.GB5854@lst.de \
--to=hch@lst.de \
--cc=dan.j.williams@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=tj@kernel.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).