archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <>
To: Christoph Hellwig <>
Cc: Jens Axboe <>, Keith Busch <>,
	Sagi Grimberg <>,
	linux-nvme <>,
	Linux PCI <>,
	Bjorn Helgaas <>,,
	Linux Upstreaming Team <>,
	Linux Kernel <>,
	Hannes Reinecke <>,
	Alex Williamson <>,
	Dan Williams <>
Subject: Re: [PATCH v2 2/5] nvme: rename "pci" operations to "mmio"
Date: Tue, 25 Jun 2019 11:51:28 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jun 24, 2019 at 2:16 PM Christoph Hellwig <> wrote:
> IFF we want to support it it has to be done at the PCIe layer.  But
> even that will require actual documentation and support from Intel.
> If Intel still believes this scheme is their magic secret to control
> the NVMe market and give themselves and unfair advantage over their
> competitors there is not much we can do.

Since the 2016 discussion, more documentation has been published:
Chapter 15 is entirely new, and section 15.2 provides a nice clarity
improvement of the magic regs in the AHCI BAR, which I have used in
these patches to clean up the code and add documentation in the header
(see patch 1 in this series, ahci-remap.h).

I believe there's room for further improvement in the docs here, but
it would be nice to know what you see as the blocking questions or
documentation gaps that would prevent us from continuing to develop
the fake PCI bridge approach
( We are going
to try and push Intel on this via other channels to see if we can get
a contact to help us, so it would be useful if I can include a
concrete list of what we need.

Bearing in mind that we've already been told that the NVMe device
config space is inaccessible, and the new docs show exactly how the
BIOS enforces such inaccessibility during early boot, the remaining
points you mentioned recently were:

 b) reset handling, including the PCI device removal as the last
    escalation step
 c) SR-IOV VFs and their management
 d) power management

Are there other blocking questions you would require answers to?


  parent reply	other threads:[~2019-06-25  3:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  5:13 [PATCH v2 0/5] Support Intel AHCI remapped NVMe devices Daniel Drake
2019-06-20  5:13 ` [PATCH v2 1/5] ahci: Discover Intel " Daniel Drake
2019-06-20  5:13 ` [PATCH v2 2/5] nvme: rename "pci" operations to "mmio" Daniel Drake
2019-06-20  6:10   ` Christoph Hellwig
2019-06-20  8:11     ` Daniel Drake
2019-06-24  6:16       ` Christoph Hellwig
2019-06-24  6:58         ` David Woodhouse
2019-06-25  3:51         ` Daniel Drake [this message]
2019-06-28  7:23           ` Christoph Hellwig
2019-06-20  5:13 ` [PATCH v2 3/5] nvme: introduce nvme_dev_ops Daniel Drake
2019-06-20  5:13 ` [PATCH v2 4/5] nvme: move common definitions to pci.h Daniel Drake
2019-06-20  5:13 ` [PATCH v2 5/5] nvme: Intel AHCI remap support Daniel Drake

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).