Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp53265pxa; Fri, 21 Aug 2020 00:32:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwxz45SJb3PsIq8Jcy8hwoIGGBLuUF3vvfp35yMbTPpXmzMC3S1YjiaxL1cGK6wAUiLeT65 X-Received: by 2002:a05:6402:b45:: with SMTP id bx5mr1609501edb.22.1597995140957; Fri, 21 Aug 2020 00:32:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597995140; cv=none; d=google.com; s=arc-20160816; b=psPRd48R01Tu3O3abVJP/RvL3kxGBbZwIMl1AeDRfHqKce36+fsh3QLHXYGABrU2X5 3EMuhubrEpADbL9B3VV5H3Gnh6nZ1wgyVyMwyUoawaTYivIeryuONklU32MUBh5a1NDQ jct2gzusbuKxRTBF+i1tlZTseMK87qGjXCr0f0n5IpTixvl62p5ZfVXOuxKHzBEUnmyT bIitFH2xHiL4FxhtprLkHATPaO02U2R3VPfhfBZXMUUXE0/XTXgvkxy0wRWHqR1P31Jr BqUQ5z5QMsO1D3bu/4h7mkNMegLmPdL0DwZGw0IiJ2RJ9ywhdzvWYV9836UlXtnaESbo uBUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:subject:from; bh=HxkSWXmeuEiyxUbxdPW/Urj7oF76h047N5MqWYw8Ufk=; b=udylU09vN/kua3+UxuwTbJzr1lWu1+R/DIn7XL3v1AqnkwaIq3MM2i6Bg43AgExPtV PGTL8+dQU9Wmg8lPLmNFC4Mb6aSBsFArvxI+IIZpuWhiIBXg8dK86Lk6m0s8QQO5IVoQ EFWb96PqiaKRJV6KVhZqvFru6nfuBY1ygLrKYFvh0KCSF5/7TiCYh262C/O53BPbjBh4 hlFmv3HBs5eukJItacO11shutwdJYSjJJxYrITzKTEkzZFQJ8iHrvsZtHqNyvtAvd4pj RybhB2i2mBvJ+q9NK2As5TswuIePt3VA6/GEMRXFm6mIL36xikbDqs19N+EDAgjm18Y3 eRNg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r25si634868edw.333.2020.08.21.00.31.57; Fri, 21 Aug 2020 00:32:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727924AbgHUHa2 (ORCPT + 99 others); Fri, 21 Aug 2020 03:30:28 -0400 Received: from lhrrgout.huawei.com ([185.176.76.210]:2679 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726864AbgHUHa1 (ORCPT ); Fri, 21 Aug 2020 03:30:27 -0400 Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 484C6D3BA6AE77980649; Fri, 21 Aug 2020 08:30:26 +0100 (IST) Received: from [127.0.0.1] (10.47.8.200) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 21 Aug 2020 08:30:25 +0100 From: John Garry Subject: Re: v5.9-rc1 commit reliably breaks pci nvme detection To: Christoph Hellwig , Jens Axboe CC: Sagi Grimberg , Chaitanya Kulkarni , , , "Ahmed S. Darwish" , Keith Busch References: <20200817135011.GA2072@lx-t490> <20200817155658.GB1221871@dhcp-10-100-145-180.wdl.wdc.com> <2356f514-9408-6a6f-871d-046984963533@kernel.dk> <20200820170729.GA4116@lx-t490> <83a3d1b6-1eb5-859b-3c5c-287d8d18a99b@kernel.dk> <20200820171214.GA15207@infradead.org> Message-ID: Date: Fri, 21 Aug 2020 08:28:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <20200820171214.GA15207@infradead.org> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.8.200] X-ClientProxiedBy: lhreml728-chm.china.huawei.com (10.201.108.79) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/08/2020 18:12, Christoph Hellwig wrote: > On Thu, Aug 20, 2020 at 11:10:58AM -0600, Jens Axboe wrote: >> To be fair, I've only heard this one complaint about it, so hopefully it's >> not too widespread. I'm on an x86-64 laptop myself with nvme, and it works >> just fine:-) > The cause for this is the weird NVMe of by ones, where 0 in a field > means 1. I thought that this was a common trick by spec writers to fit a number in range (0, 2^x] in x bits (as opposed to x+1).