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.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FAKE_REPLY_C,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 69302C2D0D1 for ; Fri, 20 Dec 2019 00:04:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3DC2A2467F for ; Fri, 20 Dec 2019 00:04:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576800242; bh=sWq+9KSTwARofQnWsAgQYWAF/MTYTslzXC2YUL9YOUU=; h=Date:From:To:Cc:Subject:In-Reply-To:List-ID:From; b=ok7kWA+5xyVEIkz3KAs2hKYvmm6WzXcE94eb7uArWKOZpMUYB0tN5+bCkeSRtAPDp SM4/WMoiFeR/ghiKCsiBQCmUU11BG5KWHcrPv7yMu7/RujDE/vMpmpGopUx0J2/ch9 oaWreXudn8R0QkFHMP2XvK7OH0hNll+1UQvtxZ+g= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727119AbfLTAEB (ORCPT ); Thu, 19 Dec 2019 19:04:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:59032 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726952AbfLTAEB (ORCPT ); Thu, 19 Dec 2019 19:04:01 -0500 Received: from localhost (mobile-166-170-223-177.mycingular.net [166.170.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0C760222C2; Fri, 20 Dec 2019 00:03:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576800240; bh=sWq+9KSTwARofQnWsAgQYWAF/MTYTslzXC2YUL9YOUU=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=y+50dcG+enUsbey/BuOFRBNPTJ0WXZMkKA4w3HQR8Zq9UY4xlF9eE9X9r3HB83JsG YXU+8e9uE7GM/4pbXGCwANX9kLhlNTxzRvHiO+5KKzDk1ZDS/LL4uxhHBgplVK70tr kxQ4OhrPB7NEa333uI4sMwoH07mSCW/ACcbQ6EYc= Date: Thu, 19 Dec 2019 18:03:58 -0600 From: Bjorn Helgaas To: Nicholas Johnson Cc: "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , Mika Westerberg , Benjamin Herrenschmidt , Logan Gunthorpe Subject: Re: [PATCH v12 0/4] PCI: Patch series to improve Thunderbolt enumeration Message-ID: <20191220000358.GA126443@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 18, 2019 at 12:54:25AM +0000, Nicholas Johnson wrote: > On Tue, Dec 17, 2019 at 09:12:48AM -0600, Bjorn Helgaas wrote: > > On Mon, Dec 09, 2019 at 12:59:29PM +0000, Nicholas Johnson wrote: > > > Hi all, > > > > > > Since last time: > > > Reverse Christmas tree for a couple of variables > > > > > > Changed while to whilst (sounds more formal, and so that > > > grepping for "while" only brings up code) > > > > > > Made sure they still apply to latest Linux v5.5-rc1 > > > > > > Kind regards, > > > Nicholas > > > > > > Nicholas Johnson (4): > > > PCI: Consider alignment of hot-added bridges when distributing > > > available resources > > > PCI: In extend_bridge_window() change available to new_size > > > PCI: Change extend_bridge_window() to set resource size directly > > > PCI: Allow extend_bridge_window() to shrink resource if necessary > > > > I have tentatively applied these to pci/resource for v5.6, but I need > > some kind of high-level description for why we want these changes. > I could not find these in linux-next (whereas it was almost immediate > last time), so this must be why. > > > The commit logs describe what the code does, and that's good, but we > > really need a little more of the *why* and what the user-visible > > benefit is. I know some of this was in earlier postings, but it seems > > to have gotten lost along the way. > > Is this explanation going into the commit notes, or is this just to get > it past reviewers, Greg K-H and Linus Torvalds? This is for the commit log of the merge commit, i.e., it should answer the question of "why should we merge this branch?" Typically this is short, e.g., here's the merge commit for the pci/resource branch that was merged for v5.5: commit 774800cb099f ("Merge branch 'pci/resource'") Author: Bjorn Helgaas Date: Thu Nov 28 08:54:36 2019 -0600 Merge branch 'pci/resource' - Protect pci_reassign_bridge_resources() against concurrent addition/removal (Benjamin Herrenschmidt) - Fix bridge dma_ranges resource list cleanup (Rob Herring) - Add PCI_STD_NUM_BARS for the number of standard BARs (Denis Efremov) - Add "pci=hpmmiosize" and "pci=hpmmioprefsize" parameters to control the MMIO and prefetchable MMIO window sizes of hotplug bridges independently (Nicholas Johnson) - Fix MMIO/MMIO_PREF window assignment that assigned more space than desired (Nicholas Johnson) - Only enforce bus numbers from bridge EA if the bridge has EA devices downstream (Subbaraya Sundeep) * pci/resource: PCI: Do not use bus number zero from EA capability PCI: Avoid double hpmemsize MMIO window assignment PCI: Add "pci=hpmmiosize" and "pci=hpmmioprefsize" parameters PCI: Add PCI_STD_NUM_BARS for the number of standard BARs PCI: Fix missing bridge dma_ranges resource list cleanup PCI: Protect pci_reassign_bridge_resources() against concurrent addition/removal The logs for individual commits are obviously longer but should answer the same question in more detail. Basically, I'm not comfortable asking Linus to pull material unless I can explain what the benefit is. I'm still struggling to articulate the benefit in this case. I think it makes hotplug work better in some cases where we need more alignment than we currently have, but that's pretty sketchy. Bjorn