All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] nvme-pci: Shutdown the device if D3Cold is allowed by the user
Date: Thu, 5 Dec 2024 19:49:34 -0600	[thread overview]
Message-ID: <20241206014934.GA3081609@bhelgaas> (raw)
In-Reply-To: <20241205232900.GA3072557@bhelgaas>

On Thu, Dec 05, 2024 at 05:29:00PM -0600, Bjorn Helgaas wrote:
> On Sat, Nov 23, 2024 at 02:31:13PM +0530, Manivannan Sadhasivam wrote:
> > On Fri, Nov 22, 2024 at 04:20:50PM -0600, Bjorn Helgaas wrote:
> > > On Mon, Nov 18, 2024 at 01:53:44PM +0530, Manivannan Sadhasivam wrote:
> > > > PCI core allows users to configure the D3Cold state for each PCI
> > > > device through the sysfs attribute
> > > > '/sys/bus/pci/devices/.../d3cold_allowed'. This attribute sets
> > > > the 'pci_dev:d3cold_allowed' flag and could be used by users to
> > > > allow/disallow the PCI devices to enter D3Cold during system
> > > > suspend.
> ...

> > We did attempt to solve this problem in multiple ways, but the
> > lesson learned was, kernel cannot decide the power mode without help
> > from userspace. That's the reason I wanted to make use of this
> > 'd3cold_allowed' sysfs attribute to allow userspace to override the
> > D3Cold if it wants based on platform requirement.
> 
> It seems sub-optimal that this only works how you want if the user
> intervenes.

Oops, I think I got this part backwards.  The patch uses PCI PM if
d3cold_allowed is set, and it's set by default, so it does what you
need for the Qualcomm platform *without* user intervention.

But I guess using the flag allows users in other situations to force
use of NVMe power management by clearing d3cold_allowed via sysfs.
Does that mean some unspecified other platforms might only work
correctly with that user intervention?


  reply	other threads:[~2024-12-06  1:49 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  8:23 [PATCH] nvme-pci: Shutdown the device if D3Cold is allowed by the user Manivannan Sadhasivam
2024-11-18 12:58 ` Christoph Hellwig
2024-11-18 14:58   ` Manivannan Sadhasivam
2024-11-22 22:20 ` Bjorn Helgaas
2024-11-23  9:01   ` Manivannan Sadhasivam
2024-11-26 17:11     ` Bjorn Andersson
2024-11-27  5:49       ` Manivannan Sadhasivam
2024-12-05 23:29     ` Bjorn Helgaas
2024-12-06  1:49       ` Bjorn Helgaas [this message]
2024-12-09 13:36         ` Christoph Hellwig
2024-12-09 14:38           ` Manivannan Sadhasivam
2024-12-12  5:59             ` Christoph Hellwig
2024-12-12 12:21               ` Rafael J. Wysocki
2024-12-12 12:49                 ` Ulf Hansson
2024-12-12 15:13                   ` Christoph Hellwig
2024-12-13 14:35                     ` Rafael J. Wysocki
2024-12-14  6:30                       ` Manivannan Sadhasivam
2024-12-16 16:23                         ` Christoph Hellwig
2024-12-16 16:42                           ` Rafael J. Wysocki
2024-12-16 16:48                             ` Manivannan Sadhasivam
2024-12-16 17:28                               ` Rafael J. Wysocki
2024-12-16 17:39                                 ` Manivannan Sadhasivam
2024-12-16 19:10                                   ` Rafael J. Wysocki
2024-12-20 15:15                             ` Konrad Dybcio
2024-12-21  3:38                               ` Manivannan Sadhasivam
2024-12-21 11:17                                 ` Konrad Dybcio
2024-12-26 16:22                                   ` Manivannan Sadhasivam
2025-01-03  7:28                               ` Christoph Hellwig
2025-01-03 11:48                                 ` Konrad Dybcio
2024-12-16 16:24                         ` Rafael J. Wysocki
2024-12-16 17:11                           ` Manivannan Sadhasivam
2024-12-16 17:35                             ` Rafael J. Wysocki
2024-12-16 17:52                               ` Manivannan Sadhasivam
2024-12-16 19:34                                 ` Rafael J. Wysocki
2024-12-16 19:40                                   ` Keith Busch
2024-12-16 19:43                                     ` Rafael J. Wysocki
2024-12-17  5:26                                   ` manivannan.sadhasivam
2024-12-17 19:45                                     ` Rafael J. Wysocki
2024-12-19  8:02                                       ` Manivannan Sadhasivam
2024-12-19 12:45                                         ` Rafael J. Wysocki
2024-12-19 16:41                                           ` Ulf Hansson
2024-12-19 18:28                                             ` Rafael J. Wysocki
2025-01-03  7:26                                               ` Christoph Hellwig
2024-12-19  6:30                                 ` Christoph Hellwig
2024-12-19  8:03                                   ` Manivannan Sadhasivam
2024-12-09 14:43         ` Manivannan Sadhasivam
2024-12-09 14:57       ` Manivannan Sadhasivam

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=20241206014934.GA3081609@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andersson@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=rjw@rjwysocki.net \
    --cc=sagi@grimberg.me \
    --cc=ulf.hansson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.