linux-kernel - Re: [PATCH] nvme-pci: Force NVME_QUIRK_SIMPLE

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 for Android: free password hash cracker in your pocket

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

Message-ID: <ZxvOEOXzLIsbEbve@kbusch-mbp.dhcp.thefacebook.com>
Date: Fri, 25 Oct 2024 10:57:52 -0600
From: Keith Busch <kbusch@...nel.org>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Konrad Dybcio <konradybcio@...nel.org>, Jens Axboe <axboe@...nel.dk>,
	Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
	Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
	Marijn Suijten <marijn.suijten@...ainline.org>,
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme-pci: Force NVME_QUIRK_SIMPLE_SUSPEND on Qualcomm
 hosts

On Fri, Oct 25, 2024 at 06:40:23PM +0200, Konrad Dybcio wrote:
> On 25.10.2024 6:12 PM, Keith Busch wrote:
> > On Thu, Oct 24, 2024 at 07:33:07PM +0200, Konrad Dybcio wrote:
> >> From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> >>
> >> The Qualcomm SC8280XP SoC requires that all PCIe hosts are powered down
> >> before the platform can reach S3-like sleep states. This is very much
> >> similar in nature to the issue described in [1].
> > 
> > The "SIMPLE" quirk is only supposed to affect kernel managed runtime
> > suspend states, s2idle or s0ix. Shouldn't s3 already be using the simple
> > suspend?
> 
> So on these platforms, all system sleep states (incl. S3) are entered
> through what Linux sees as s2idle, with a separate MCU doing a lot
> behind the scenes. s2idle of course also covers the runtime cpuidle
> cases.
> 
> All but the deepest state (which Linux doesn't differentiate as of
> today) are effectively somewhat like s0ix.
> It's a bit hard to draw accurate lines between Intel terminology and
> what we have here, as there's way more things onboard than just the CPU
> cluster that may be operating independently..

Gotcha.

Is there any sleep state on this where using the nvme managed power is
advantageous, or is the simple suspend preferred in every scenario for
this platform?