Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp627333iog; Fri, 24 Jun 2022 10:29:34 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vWi/72K+VvkD/DFJQNObesyjzQkATCf61qSRZY+YgQkr679Nkqqvdmw+Fq0ietwgVWL1HS X-Received: by 2002:a05:6402:84a:b0:423:fe99:8c53 with SMTP id b10-20020a056402084a00b00423fe998c53mr187265edz.195.1656091774270; Fri, 24 Jun 2022 10:29:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656091774; cv=none; d=google.com; s=arc-20160816; b=ffAQT/tZpGUnrj7jDrYek9+mFg7mEo9IwxhvhfNJaKOIG5PrS3UlTk8+3TaN347xpY l7a7kLYB0JGRM0omt3v6kbSOKFh5AgEhgNOuK9w1KGZiOWM81VZvoXTawSfyeTowvJhX svYguCPqinoweVguM1cb3Wduiqhbr2IJxGl5HcklGapvGX1jUamkO4dnoM9+AataKytB OH/mkPAuylrcV82ZyugiCUZ6bmy+g6dqdWM1/JA61CV+6xMOyWo4z7XlISu5t6yrzLf0 yLSwv6zKYXx3ay7uS0dV9F9/sqXu8MZXQo3wESsINTqE3H84k3E+cP0scqsQXc0mhQzP G2Sw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=AutafhSibQoUBHvGSjeOa5jVdX+wWOVUBtPvq4I3Y0E=; b=QEZ4PmQat8oLkzc7vgzR+P+RBbkKHGaJ43Xvjk13m1XuRKhAbchnj13s8MVwZRe5yX 7smGrJUmsAJUlLUtGEE4L4Vp2KaoKreW6CbSfI/HMDsxqIzaKgycHbE4nlcuKjaFoc9u qCDB6lvv/gI+Ue1dev+3NxWfCJ0K1oHAde2+rJue+c6if2IZIA00AJMhw/ktFZMQZmgB tN4l6OAOMMD8my7lO6KrCWnOCtSpgyphfC1ny+RULrEbMzAwv7oq1bfnYo8E4l8wdrRQ AIE/32ZPRvV6XI7ijrgos64zYfFp9Zs2nG7g1QFMF/4e+9iwRys62GMCfl1eGFzbmGqP j2Cg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z19-20020a056402275300b0042e1a7667f7si4218672edd.613.2022.06.24.10.29.08; Fri, 24 Jun 2022 10:29:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231991AbiFXRSQ (ORCPT + 99 others); Fri, 24 Jun 2022 13:18:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38482 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231166AbiFXRSP (ORCPT ); Fri, 24 Jun 2022 13:18:15 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C69CF1E3E1 for ; Fri, 24 Jun 2022 10:18:12 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 8E11392009C; Fri, 24 Jun 2022 19:18:11 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 86F1F92009B; Fri, 24 Jun 2022 18:18:11 +0100 (BST) Date: Fri, 24 Jun 2022 18:18:11 +0100 (BST) From: "Maciej W. Rozycki" To: Palmer Dabbelt cc: Paul Walmsley , Albert Ou , Bjorn Helgaas , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PING^2][PATCH] RISC-V: PCI: Avoid handing out address 0 to devices In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Jun 2022, Palmer Dabbelt wrote: > > > Therefore avoid handing out address 0, by bumping the lowest address > > > available to PCI via PCIBIOS_MIN_IO and PCIBIOS_MIN_MEM up by 4 and 16 > > > respectively, which is the minimum allocation size for I/O and memory > > > BARs. > > > > Ping for: > > > > Sorry, I got this mixed up with the non-RISC-V patch. If you mean this: then we just don't have consensus to move forward. If we ever do for a generic change, then we can revert the RISC-V platform solution, as it's merely an internal implementation detail and not a part of the ABI or something. > David poked me about > it, this is on for-next. It's passing my tests, but they're just QEMU so > probably not all that exciting here. Thanks! I don't know offhand what QEMU supports as far as the RISC-V architecture is concerned; I guess you can't just enable a PCI port-I/O serial port in the simulator and see if it works with Linux or not. Anyway it's just number shuffling, so the change should be reasonably safe. Maciej