[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210527114029.GC17266@lst.de>
Date: Thu, 27 May 2021 13:40:29 +0200
From: Christoph Hellwig <hch@....de>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, Christoph Hellwig <hch@....de>,
Keith Busch <kbusch@...nel.org>,
Koba Ko <koba.ko@...onical.com>, Jens Axboe <axboe@...com>,
Sagi Grimberg <sagi@...mberg.me>,
linux-nvme <linux-nvme@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Henrik Juul Hansen <hjhansen2020@...il.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Linux PCI <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] nvme-pci: Avoid to go into d3cold if device can't use
npss.
On Thu, May 27, 2021 at 12:24:06AM +0800, Kai-Heng Feng wrote:
> Yes, that's exactly what they said. Because Windows Modern Standby
> always keep the NVMe at D0, so D3hot is untested by the vendors.
So all the problems we've deal with latetly are that platforms cut the
power off. So it is not kept always at D0 which would be the right thing,
but moved into D3cold.
Which makes this patch to disable D3cold rather counterintuitive.
Powered by blists - more mailing lists