[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47c4eb66-c81e-05e7-b31f-ace8b61b09fa@nvidia.com>
Date: Sat, 5 Feb 2022 22:14:06 +0530
From: Vidya Sagar <vidyas@...dia.com>
To: "Kenneth R. Crudup" <kenny@...ix.com>,
Bjorn Helgaas <helgaas@...nel.org>
CC: <bhelgaas@...gle.com>, <lorenzo.pieralisi@....com>,
<hkallweit1@...il.com>, <wangxiongfeng2@...wei.com>,
<mika.westerberg@...ux.intel.com>, <kai.heng.feng@...onical.com>,
<chris.packham@...iedtelesis.co.nz>, <yangyicong@...ilicon.com>,
<treding@...dia.com>, <jonathanh@...dia.com>, <abhsahu@...dia.com>,
<sagupta@...dia.com>, <linux-pci@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kthota@...dia.com>,
<mmaddireddy@...dia.com>, <sagar.tv@...il.com>
Subject: Re: [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for
suspend/resume
On 2/5/2022 4:47 AM, Kenneth R. Crudup wrote:
> External email: Use caution opening links or attachments
>
>
> 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).
That would be a good starting point to understand it better. In fact if
the previous problematic patch works fine on master, then, we are sure
that something in the sub-system would have fixed the issue.
I'll wait for the outcome of this experiment before re-sending my patch.
Thanks in advance Kenny for volunteering for this activity.
- Vidya Sagar
>
> -Kenny
>
> --
> Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
>
Powered by blists - more mailing lists