From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bmailout3.hostsharing.net (bmailout3.hostsharing.net [176.9.242.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B00DF30FC35 for ; Mon, 1 Dec 2025 13:26:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=176.9.242.62 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764595582; cv=none; b=C4FxQrnrd/dVWBeuX3mUrDpA2ZyzsMG+FrN296aoDOq0OkP34wzdLglo1yQZb//zSYC6kj4O37OFa71rAzg0z0M9zoVEDiOP2T92y5UuZdOSLxszaSoXBMT6BBtYNPuV+PLdc8NOBfrQmA41nA12gbNN/WioDKsHujjBI8XyW+E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764595582; c=relaxed/simple; bh=sokggr8bO/LgBuyGjRQJCRAZyeKmO4+IyJXkOVOAZqk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=m7FGmtywFbC1jjJvJBZymsY3kPf+0PVMX3+SdyhIOspGOmXlo3Vfuue6oEa76E/J3LynhMhd+B2VoCVHEDR9pNZHMNimNUf3luImdvNiE4VO8Gmi50VlOAwgJQeOtrEUVYyvpl3pzk5iOMqcN4E315f7QAP8xWlE4H8nhlBHDQ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de; spf=none smtp.mailfrom=h08.hostsharing.net; arc=none smtp.client-ip=176.9.242.62 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=h08.hostsharing.net Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "*.hostsharing.net", Issuer "GlobalSign GCC R6 AlphaSSL CA 2025" (verified OK)) by bmailout3.hostsharing.net (Postfix) with ESMTPS id A47AA2C0525E; Mon, 1 Dec 2025 14:26:17 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 71B1710A84; Mon, 1 Dec 2025 14:26:17 +0100 (CET) Date: Mon, 1 Dec 2025 14:26:17 +0100 From: Lukas Wunner To: "guanghuifeng@linux.alibaba.com" Cc: Bjorn Helgaas , linux-pci , kanie , alikernel-developer , Ilpo =?iso-8859-1?Q?J=E4rvinen?= Subject: Re: [PATCH] PCI: Fix PCIe SBR dev/link wait error Message-ID: References: <20251124104502.777141-1-guanghuifeng@linux.alibaba.com> <20251124235858.GA2726643@bhelgaas> <969657a9-ea6b-44a8-a06c-c2af52212493@linux.alibaba.com> Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <969657a9-ea6b-44a8-a06c-c2af52212493@linux.alibaba.com> On Mon, Dec 01, 2025 at 08:56:10PM +0800, guanghuifeng@linux.alibaba.com wrote: > 2025/12/1 18:03, Lukas Wunner : > > It seems highly unusual that the different functions of the same physical > > device require different delays until they're accessible. I don't think > > we can accept such a sweeping change wholesale without more details, > > so please share what the topology looks like (lspci -tv), what devices are > > involved (lspci -vvv) and which device requires extra wait time for some > > of its functions. Could you please provide the details I asked for above? Thanks, Lukas