From: Christoph Hellwig <hch@lst.de>
To: Daniel Drake <drake@endlessm.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme <linux-nvme@lists.infradead.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-ide@vger.kernel.org,
Linux Upstreaming Team <linux@endlessm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Alex Williamson <alex.williamson@redhat.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v2 2/5] nvme: rename "pci" operations to "mmio"
Date: Fri, 28 Jun 2019 09:23:10 +0200 [thread overview]
Message-ID: <20190628072310.GA28896@lst.de> (raw)
In-Reply-To: <CAD8Lp464B0dOd+ayF_AK4DRzHEpiaSbUOXjVJ5bq5zMXq=BBKQ@mail.gmail.com>
On Tue, Jun 25, 2019 at 11:51:28AM +0800, Daniel Drake wrote:
> 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:
If we can't access the config space we unfortunately can't support
this scheme at all, as it invalidates all our quirks handling.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 2/5] nvme: rename "pci" operations to "mmio"
Date: Fri, 28 Jun 2019 09:23:10 +0200 [thread overview]
Message-ID: <20190628072310.GA28896@lst.de> (raw)
In-Reply-To: <CAD8Lp464B0dOd+ayF_AK4DRzHEpiaSbUOXjVJ5bq5zMXq=BBKQ@mail.gmail.com>
On Tue, Jun 25, 2019@11:51:28AM +0800, Daniel Drake wrote:
> 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:
If we can't access the config space we unfortunately can't support
this scheme at all, as it invalidates all our quirks handling.
next prev parent reply other threads:[~2019-06-28 7:31 UTC|newest]
Thread overview: 24+ 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 ` Daniel Drake
2019-06-20 5:13 ` [PATCH v2 1/5] ahci: Discover Intel " Daniel Drake
2019-06-20 5:13 ` Daniel Drake
2019-06-20 5:13 ` [PATCH v2 2/5] nvme: rename "pci" operations to "mmio" Daniel Drake
2019-06-20 5:13 ` Daniel Drake
2019-06-20 6:10 ` Christoph Hellwig
2019-06-20 6:10 ` Christoph Hellwig
2019-06-20 8:11 ` Daniel Drake
2019-06-20 8:11 ` Daniel Drake
2019-06-24 6:16 ` Christoph Hellwig
2019-06-24 6:16 ` Christoph Hellwig
2019-06-24 6:58 ` David Woodhouse
2019-06-24 6:58 ` David Woodhouse
2019-06-25 3:51 ` Daniel Drake
2019-06-25 3:51 ` Daniel Drake
2019-06-28 7:23 ` Christoph Hellwig [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 ` 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 ` Daniel Drake
2019-06-20 5:13 ` [PATCH v2 5/5] nvme: Intel AHCI remap support Daniel Drake
2019-06-20 5:13 ` 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:
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=20190628072310.GA28896@lst.de \
--to=hch@lst.de \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=drake@endlessm.com \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.