From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65AFDC4321A for ; Fri, 28 Jun 2019 07:31:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 433652064A for ; Fri, 28 Jun 2019 07:31:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726648AbfF1Hby (ORCPT ); Fri, 28 Jun 2019 03:31:54 -0400 Received: from verein.lst.de ([213.95.11.210]:45945 "EHLO newverein.lst.de" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726408AbfF1Hbx (ORCPT ); Fri, 28 Jun 2019 03:31:53 -0400 X-Greylist: delayed 518 seconds by postgrey-1.27 at vger.kernel.org; Fri, 28 Jun 2019 03:31:53 EDT Received: by newverein.lst.de (Postfix, from userid 2407) id A014E68CFE; Fri, 28 Jun 2019 09:23:10 +0200 (CEST) Date: Fri, 28 Jun 2019 09:23:10 +0200 From: Christoph Hellwig To: Daniel Drake Cc: Christoph Hellwig , Jens Axboe , Keith Busch , Sagi Grimberg , linux-nvme , Linux PCI , Bjorn Helgaas , linux-ide@vger.kernel.org, Linux Upstreaming Team , Linux Kernel , Hannes Reinecke , Alex Williamson , Dan Williams Subject: Re: [PATCH v2 2/5] nvme: rename "pci" operations to "mmio" Message-ID: <20190628072310.GA28896@lst.de> References: <20190620051333.2235-1-drake@endlessm.com> <20190620051333.2235-3-drake@endlessm.com> <20190620061038.GA20564@lst.de> <20190624061617.GA2848@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-ide-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ide@vger.kernel.org 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.