linux-kernel - Re: [PATCH v2 0/3] PCI: Notify PCI drivers about powerdown during suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0hLtU=naptVYfp9ZmLeWzJREQ1icWJYrjh+a5LqOYG4Dw@mail.gmail.com>
Date:   Wed, 18 May 2022 15:27:22 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Keith Busch <kbusch@...nel.org>,
        Christoph Hellwig <hch@....de>,
        linux-nvme <linux-nvme@...ts.infradead.org>,
        Linux PCI <linux-pci@...r.kernel.org>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        svarbanov@...sol.com, Bjorn Andersson <bjorn.andersson@...aro.org>,
        Jens Axboe <axboe@...com>, quic_vbadigan@...cinc.com,
        quic_krichai@...cinc.com, quic_nitirawa@...cinc.com,
        Vidya Sagar <vidyas@...dia.com>,
        Sagi Grimberg <sagi@...mberg.me>,
        Linux PM <linux-pm@...r.kernel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v2 0/3] PCI: Notify PCI drivers about powerdown during suspend

On Wed, May 18, 2022 at 3:19 PM Manivannan Sadhasivam
<manivannan.sadhasivam@...aro.org> wrote:
>
> Hi,
>
> This series adds support for notifying the PCI drivers like NVMe about the
> transition of PCI devices into powerdown mode during system suspend.

What kind of system suspend are you referring to?  Suspend-to-idle or
suspend-to-RAM?

For suspend-to-RAM this series should not be necessary at all, because
drivers cannot assume that the state of devices will be preserved
anyway in this case.

For suspend-to-idle, drivers can expect the preservation of the device
state, so perhaps the firmware should be prevented from powering them
off in the suspend-to-idle path instead.