[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170209184613.GA78375@otc-nc-03>
Date: Thu, 9 Feb 2017 10:46:13 -0800
From: "Raj, Ashok" <ashok.raj@...el.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Lukas Wunner <lukas@...ner.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Bart Van Assche <bart.vanassche@...disk.com>,
Christoph Hellwig <hch@....de>,
Yinghai Lu <yinghai@...nel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Keith Busch <keith.busch@...el.com>, ashok.raj@...el.com
Subject: Re: [GIT PULL] PCI fixes for v4.10
Hi Bjorn/Lucas
I did a lspci and captured after a fresh reboot on the slot before
attempting a power off via sysfs.
lspci-at-poweron - values after a cold reset poweron.
lspci-aft-poweroff - values after a echo 0 > power
lspci-aft-poweron - values after a echo 1 > power
i would expect most or all of those values to stay same between poweron
and after the next sysfs managed poweron. Would be worth taking a look and see
if we have any escapes.
Cheers,
Ashok
On Thu, Feb 09, 2017 at 10:23:28AM -0800, Raj, Ashok wrote:
> Thanks Bjorn,
>
> With the fixes below, managed add remove via sysfs seems to work on my
> SKX system.
>
> I'm not familiar with runtime PM aspects, just started looking into it
> after this one. There seems some interactions with ASPM and how we handle
> devices that support ARI for e.g.
>
> For hotplug, we have a good set of tests to check coverage. That matrix
> might need to be expanded for runtime PM interactions.
>
> Cheers,
> Ashok
>
View attachment "lspci-at-poweron" of type "text/plain" (4158 bytes)
View attachment "lspci-aft-poweroff" of type "text/plain" (4159 bytes)
View attachment "lspci-aft-poweron" of type "text/plain" (4157 bytes)
Powered by blists - more mailing lists