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 6301BC433F5 for ; Fri, 4 Feb 2022 23:17:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377883AbiBDXRF (ORCPT ); Fri, 4 Feb 2022 18:17:05 -0500 Received: from mailbackend.panix.com ([166.84.1.89]:48910 "EHLO mailbackend.panix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234270AbiBDXRF (ORCPT ); Fri, 4 Feb 2022 18:17:05 -0500 Received: from [172.20.1.124] (50-233-66-22-static.hfc.comcastbusiness.net [50.233.66.22]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4JrBJH1BySz2q8Y; Fri, 4 Feb 2022 18:17:03 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1644016624; bh=nTN4J6gLwOwjvwUgWB10d7EMo0zm9tPlaYTEXfi+uA0=; h=Date:From:Reply-To:To:cc:Subject:In-Reply-To:References; b=e/KfhQaLRIsGDx5g8CpP1pkGEqn1V+11n09TsP18xTFN05KK7kIWdlHPwpaTrnlIp P9WCkXLct3N2Aq6h7noHqXjgeO8dcVRXLFeYcTsK0xXDKZJJNuzwhDIw19S2hVBKXT nx0gjMaRig4dOfTZuhSinSaDXOxdjeuWXLB3zH5k= Date: Fri, 4 Feb 2022 15:17:02 -0800 (PST) From: "Kenneth R. Crudup" Reply-To: "Kenneth R. Crudup" To: Bjorn Helgaas cc: Vidya Sagar , bhelgaas@google.com, lorenzo.pieralisi@arm.com, hkallweit1@gmail.com, wangxiongfeng2@huawei.com, mika.westerberg@linux.intel.com, kai.heng.feng@canonical.com, chris.packham@alliedtelesis.co.nz, yangyicong@hisilicon.com, treding@nvidia.com, jonathanh@nvidia.com, abhsahu@nvidia.com, sagupta@nvidia.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com, "Kenneth R. Crudup" Subject: Re: [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for suspend/resume In-Reply-To: <20220204230234.GA226601@bhelgaas> Message-ID: <7b377c19-23-6793-5e43-b757cfd8437@panix.com> References: <20220204230234.GA226601@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Fri, 4 Feb 2022, Bjorn Helgaas wrote: > Do we have a theory on what might have caused the regression before? > Or at least something that is different this time around? If you'd like, I could try re-applying the previous problem commit or your attempted fix on top of Linus' master if you'd like to see if something was fixed somewhere else in the PCIe subsystem, but if you think it's not worth- while I'm satisfied with the current fix (or probably more-exactly for my particular machine, lack of regression). -Kenny -- Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA