public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	linux-ide@vger.kernel.org, mika.westerberg@intel.com,
	anshuman.gupta@intel.com, "Kurmi,
	Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
	"Saarinen, Jani" <jani.saarinen@intel.com>,
	lucas.demarchi@intel.com
Subject: Re: Regression on linux-next (next-20250708)
Date: Tue, 29 Jul 2025 07:33:59 +0900	[thread overview]
Message-ID: <5143bbee-697b-4357-9645-10f38296b561@kernel.org> (raw)
In-Reply-To: <d34d122f-2ef8-44f1-83c9-92c7b9e83b6e@intel.com>

On 7/29/25 01:24, Borah, Chaitanya Kumar wrote:
> 
> 
> On 7/28/2025 9:41 AM, Damien Le Moal wrote:
>> On 7/25/25 3:43 PM, Borah, Chaitanya Kumar wrote:
>>> For some context in our kms_pm_rpm tests, we enable min_power policy for SATA
>>> so that we can reach deep runtime power states and restore the original policy
>>> after finishing. [5][6]
>>>
>>> IIUC, the above change is based on spec and not something which can be
>>> reverted. So as I see it, we have to drop this code path for external ports.
>>> However I am not sure if we can achieve deep power states without enforcing it
>>> through the sysfs entry.
>>>
>>> Atleast for the basic-rte subtest, the test passes if we comment out the
>>> functions controlling the SATA ports. We will need more testing to determine if
>>> this approach work. Any thoughts on it?
>>>
>>> Also, are there other ways to detect a port is external other than receiving
>>> EOPNOTSUPP on the sysfs write?
>>
>> The attached patch adds the "link_power_management_supported" sysfs device
>> attribute for drives connected to AHCI. Would that work for you ?
>>
> 
> Yes this could work. I quickly hacked the test to ignore writing policy 
> if this file returns 0.
> 
> Here is the state of the machine I am testing on.
> 
> /sys/class/scsi_host/host0/link_power_management_supported: 0
> /sys/class/scsi_host/host1/link_power_management_supported: 0
> /sys/class/scsi_host/host2/link_power_management_supported: 0
> /sys/class/scsi_host/host3/link_power_management_supported: 0
> /sys/class/scsi_host/host4/link_power_management_supported: 1
> /sys/class/scsi_host/host5/link_power_management_supported: 1
> /sys/class/scsi_host/host6/link_power_management_supported: 1
> /sys/class/scsi_host/host7/link_power_management_supported: 1

Looks good. My test machine looks exactly like this too.
I will send out this patch as it is useful anyway regardless of external/hotplug
ports since not all adapters/drives support LPM.

When posting this, can I tag it as a solution to the regression ?

And in addition to this patch, I will work on a flexible way of ignoring hotplug.


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-07-28 22:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  6:43 Regression on linux-next (next-20250708) Borah, Chaitanya Kumar
2025-07-25 10:33 ` Damien Le Moal
2025-07-28 16:37   ` Borah, Chaitanya Kumar
2025-07-28 22:20     ` Damien Le Moal
2025-07-28  4:11 ` Damien Le Moal
2025-07-28 16:24   ` Borah, Chaitanya Kumar
2025-07-28 22:33     ` Damien Le Moal [this message]
2025-07-29  8:43       ` Borah, Chaitanya Kumar
2025-07-28  5:31 ` Damien Le Moal
2025-07-28 16:33   ` Borah, Chaitanya Kumar
2025-07-28 22:30     ` Damien Le Moal
2025-07-29  8:58       ` Borah, Chaitanya Kumar

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=5143bbee-697b-4357-9645-10f38296b561@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=anshuman.gupta@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=mika.westerberg@intel.com \
    --cc=suresh.kumar.kurmi@intel.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