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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54600C4332F for ; Tue, 13 Dec 2022 15:09:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235777AbiLMPJ4 (ORCPT ); Tue, 13 Dec 2022 10:09:56 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49174 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236095AbiLMPJj (ORCPT ); Tue, 13 Dec 2022 10:09:39 -0500 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D706B64DF for ; Tue, 13 Dec 2022 07:09:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670944178; x=1702480178; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=rSSMwIQD+G+i9tnloMHYHmBwBmpvRTkXzg0Lp62Cfrk=; b=fXqNP/KWXI2hCk/vAfD6FU7mege9STBljBqBOWXw3neP429t2evPOH/M qfvBbQSNpLYhpjkGTWgGsBTBFkGZRsGjf+I9A/s7p874y3D4yG/qXfXRE WZ3WGi0PdCnWO7IJ7c/GFDejdDoVRGHlN7eBkbRG6Fw5am59b5DoqJ8XP Wff35SHwtFXdxxAF+bU7yWQHcMbhURxCv6niialHevPxMD7uLB/y5owv+ MElmPuJ19Y7sYBUWeG0bDN8SU4rJvoHhgUdqYd62hloKxrW12FPPRgYgL o2L0x00xAUDKVeEfGtYRbkWTYlcYOQrh4sh3N44/kmEZPZv996wz6fbaA g==; X-IronPort-AV: E=McAfee;i="6500,9779,10560"; a="315788707" X-IronPort-AV: E=Sophos;i="5.96,241,1665471600"; d="scan'208";a="315788707" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2022 07:09:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10560"; a="737422020" X-IronPort-AV: E=Sophos;i="5.96,241,1665471600"; d="scan'208";a="737422020" Received: from black.fi.intel.com ([10.237.72.28]) by FMSMGA003.fm.intel.com with ESMTP; 13 Dec 2022 07:09:36 -0800 Received: by black.fi.intel.com (Postfix, from userid 1001) id 58857F7; Tue, 13 Dec 2022 17:10:05 +0200 (EET) Date: Tue, 13 Dec 2022 17:10:05 +0200 From: Mika Westerberg To: Alexander Motin Cc: Bjorn Helgaas , Nicholas Johnson , Nick Wolff , Bjorn Helgaas , linux-pci@vger.kernel.org Subject: Re: pci_bus_distribute_available_resources() is wrong? Message-ID: References: <2ec11223-edb3-5f5c-62cd-3532d92de0a4@ixsystems.com> <6053736d-1923-41e7-def9-7585ce1772d9@ixsystems.com> <35208ffe-0aee-b055-0ed7-99b6414af6da@ixsystems.com> <2f49eee1-7c72-8281-50c1-debaccd43c81@ixsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2f49eee1-7c72-8281-50c1-debaccd43c81@ixsystems.com> Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org Hi, On Tue, Dec 13, 2022 at 10:00:42AM -0500, Alexander Motin wrote: > On 13.12.2022 09:48, Mika Westerberg wrote: > > On Tue, Dec 13, 2022 at 09:11:12AM -0500, Alexander Motin wrote: > > > > I'm also more than happy to test any patches regarding this if someone > > > > else wants to work on it ;-) > > > > > > I was kind of ready to dive in, I hate hacks and tunables to workaround > > > bugs. But as I have told, I see this code first time, so my solutions may > > > appear not right. But I'll help as I can, if needed. > > > > That's good to hear :) Okay feel free to use any of my previous patches > > as base if needed. I can test the Thunderbolt/USB4 and the QEMU PCI/PCIe > > topologies so please keep me in the loop when submitting. > > It is quite a quick change of roles, don't you find? It is you created the > problem. It is your email includes "@linux.intel.com" here. Don't you feel > some responsibility? ;) Sorry I must have misunderstood what you meant then. I was under impression that you were ready to go and fix the issue. Okay no problem I will work on this myself then and keep you guys updated. > Where are the current result of "I'm working on a new version of the patch > series that should take these into consideration"? Still early "draft" I will submit it once it is in better shape (and I have validated it works in the known cases). Anyway it will happen after the merge window is closed.