From: Bjorn Helgaas <helgaas@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: "Kenneth R. Crudup" <kenny@panix.com>,
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
Subject: Re: [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for suspend/resume
Date: Fri, 4 Feb 2022 17:02:34 -0600 [thread overview]
Message-ID: <20220204230234.GA226601@bhelgaas> (raw)
In-Reply-To: <708b746c-1715-9d64-5a59-55c9ad81bd0a@nvidia.com>
On Wed, Feb 02, 2022 at 09:47:06AM +0530, Vidya Sagar wrote:
> On 2/2/2022 3:55 AM, Kenneth R. Crudup wrote:
> > On Wed, 2 Feb 2022, Vidya Sagar wrote:
> > > BTW, I see that the ASPM L1SS capability is supported by only
> > > two endpoints viz. KIOXIA's NVMe drive and Realtek's Card
> > > reader. None of the root ports seem to have the support. So, I'm
> > > wondering how was it even getting enabled in the first place
> > > earlier?
> >
> > > (OR)
> >
> > > was it the case that L1SS sub-states were never enabled earlier
> > > also and the issue was occurring without having ASPM L1SS
> > > enabled? (but with only L0s and L1 enabled??)
> >
> > I'm not proficient enough in PCIe to be able to be sure of the
> > answers to those- what can/could I do to determine this?
>
> Nothing at this point, but could you please confirm that you are
> using the same system as before? if that is the case, then, I'm not
> sure how is it possible that the earlier patch which is also for
> saving/restoring L1SS registers could affect a system that doesn't
> even support L1SS.
>
> Bjorn, any thoughts on this?
Do we have a theory on what might have caused the regression before?
Or at least something that is different this time around?
There's been a lot of discussion on this thread, so I'm going to
ignore this patch for now. If you think it's good to go, please post
it again with the relevant Tested-bys and a note about why we think it
should work this time when it didn't last time.
Bjorn
> > > Also, I see that from 'before' and 'after' logs that for both
> > > NVMe and Card reader and their corresponding root ports, none of
> > > the ASPM states are enabled (not even L0s or L1).
> > > Did you set the policy to 'powersupersave' before hibernating
> > > the system?
> >
> > Yeah:
> >
> > CONFIG_PCIEASPM_POWER_SUPERSAVE=y
> >
> > My laptop loses ~1.5%/hr in S3; I was trying anything I could to reduce that,
> > if possible.
> >
> > -Kenny
> >
> > --
> > Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
> >
next prev parent reply other threads:[~2022-02-04 23:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 12:35 [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-02-01 13:54 ` Kenneth R. Crudup
[not found] ` <8aa96f79-402-4897-424f-64a2c6893de8@panix.com>
2022-02-01 19:03 ` Kenneth R. Crudup
2022-02-01 19:05 ` Kenneth R. Crudup
2022-02-01 19:10 ` Kenneth R. Crudup
2022-02-01 19:24 ` Vidya Sagar
2022-02-01 22:25 ` Kenneth R. Crudup
2022-02-02 4:17 ` Vidya Sagar
2022-02-04 1:18 ` Kenneth R. Crudup
2022-02-04 5:37 ` Vidya Sagar
2022-02-04 23:02 ` Bjorn Helgaas [this message]
2022-02-04 23:17 ` Kenneth R. Crudup
2022-02-05 16:44 ` Vidya Sagar
[not found] ` <12fe557f-7336-1970-d8f0-5a93529cf8c1@panix.com>
2022-02-05 17:32 ` Kenneth R. Crudup
2022-02-05 17:33 ` Kenneth R. Crudup
2022-02-07 16:33 ` Bjorn Helgaas
2022-02-07 18:20 ` Kenneth R. Crudup
2022-02-15 13:10 ` Kenneth R. Crudup
2022-02-16 4:40 ` Vidya Sagar
2022-02-16 6:00 ` Kenneth R. Crudup
2022-02-16 13:11 ` Vidya Sagar
2022-04-12 22:50 ` Bjorn Helgaas
2022-04-13 0:19 ` Kai-Heng Feng
2022-04-14 16:41 ` Bjorn Helgaas
2022-04-15 14:26 ` Kai-Heng Feng
2022-04-15 21:25 ` Bjorn Helgaas
2022-04-21 6:16 ` Kai-Heng Feng
2022-04-21 20:36 ` Bjorn Helgaas
2022-04-21 20:40 ` Kenneth R. Crudup
2022-04-21 21:11 ` Bjorn Helgaas
2022-04-21 21:21 ` Kenneth R. Crudup
2022-04-13 13:26 ` Bjorn Helgaas
2022-11-23 21:44 ` Matthias Kaehlcke
2022-11-23 22:01 ` Kenneth R. Crudup
2022-11-24 0:07 ` Matthias Kaehlcke
2022-02-15 13:12 ` Kenneth R. Crudup
2022-02-04 11:23 ` Abhishek Sahu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220204230234.GA226601@bhelgaas \
--to=helgaas@kernel.org \
--cc=abhsahu@nvidia.com \
--cc=bhelgaas@google.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=hkallweit1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kai.heng.feng@canonical.com \
--cc=kenny@panix.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=sagupta@nvidia.com \
--cc=treding@nvidia.com \
--cc=vidyas@nvidia.com \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyicong@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).