All of lore.kernel.org
 help / color / mirror / Atom feed
From: kai.heng.feng@canonical.com (Kai Heng Feng)
Subject: [PATCHv2 6/6] nvme-pci: Use host managed power state for suspend
Date: Wed, 22 May 2019 14:47:57 +0800	[thread overview]
Message-ID: <D4CDCA72-A3B8-4717-9ED2-A14254C78963@canonical.com> (raw)
In-Reply-To: <CAJZ5v0gLqL7GUjwz5F8=9Fc-W2n3FRzbbB2L8udaXgN4Vsd8-Q@mail.gmail.com>

at 6:34 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:

> On Fri, May 17, 2019@11:35 AM Christoph Hellwig <hch@lst.de> wrote:
>> On Fri, May 17, 2019@11:17:52AM +0200, Rafael J. Wysocki wrote:
>>> AFAICS, using DMA while creating a hibernation snapshot image of
>>> memory would not be a good idea, so the host memory buffer should be
>>> disabled during the "freeze" stage or hibernation (and it can be
>>> re-enabled when that stage is complete).
>>
>> Once we'd disable the HMB the harm is done, so no point in re-enabling it.
>
> But after the "freeze" stage the image may need to be written to the
> device, so I guess it would be useful to enable the HMB for that?
>
>> What would this mean in terms of ops?  Only disable in freeze_noirq?
>
> It can be disabled in any of the "freeze" callbacks (freeze,
> freeze_late, freeze_irq) where it makes most sense.  I also would
> re-enable it in the complementary "thaw" one, in case the device will
> be used to store the image.
>
>> Or stick to the simple ops and find another helper that indicates we are  
>> doing a hibernation?
>
> There are no helpers for that, it needs to be done manually, sort of.

I've got confirmation from Vendor, disabling HMB isn?t necessary when the  
host stays at D0, which is what we use in S2I.
I?ve done some testing and I can confirm S2I suspend/resume can work  
without disabling HMB.

Kai-Heng

  reply	other threads:[~2019-05-22  6:47 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 16:36 [PATCH 1/6] nvme-pci: Fix controller freeze wait disabling Keith Busch
2019-05-15 16:36 ` [PATCH 2/6] nvme-pci: Don't disable on timeout in reset state Keith Busch
2019-05-16  3:07   ` Ming Lei
2019-05-16 14:33     ` Keith Busch
2019-05-16  6:27   ` Christoph Hellwig
2019-05-15 16:36 ` [PATCH 3/6] nvme-pci: Unblock reset_work on IO failure Keith Busch
2019-05-16  3:13   ` Ming Lei
2019-05-16 14:14     ` Keith Busch
2019-05-17  2:31       ` Ming Lei
2019-05-16  6:28   ` Christoph Hellwig
2019-05-15 16:36 ` [PATCH 4/6] nvme-pci: Sync queues on reset Keith Busch
2019-05-16  3:34   ` Ming Lei
2019-05-16  6:29   ` Christoph Hellwig
2019-05-16 14:08     ` Keith Busch
2019-05-16 13:43   ` Minwoo Im
2019-05-15 16:36 ` [PATCH 5/6] nvme: Export get and set features Keith Busch
2019-05-16  6:26   ` Christoph Hellwig
2019-05-16 13:47   ` Minwoo Im
2019-05-15 16:36 ` [PATCHv2 6/6] nvme-pci: Use host managed power state for suspend Keith Busch
2019-05-15 19:33   ` Mario.Limonciello
2019-05-15 19:34     ` Keith Busch
2019-05-15 19:43       ` Mario.Limonciello
2019-05-16  6:25   ` Christoph Hellwig
2019-05-16 14:24     ` Keith Busch
2019-05-17  9:08       ` Christoph Hellwig
2019-05-16  9:29   ` Rafael J. Wysocki
2019-05-16 14:26     ` Keith Busch
2019-05-16 18:27       ` Kai-Heng Feng
2019-05-16 18:33         ` Mario.Limonciello
2019-05-16 19:38           ` Keith Busch
2019-05-16 20:25             ` Rafael J. Wysocki
2019-05-16 20:39               ` Keith Busch
2019-05-16 20:56                 ` Rafael J. Wysocki
2019-05-17  8:39                   ` Rafael J. Wysocki
2019-05-17  9:05                     ` Christoph Hellwig
2019-05-17  9:17                       ` Rafael J. Wysocki
2019-05-17  9:35                         ` Christoph Hellwig
2019-05-17 10:34                           ` Rafael J. Wysocki
2019-05-22  6:47                             ` Kai Heng Feng [this message]
2019-05-22 15:52                               ` Christoph Hellwig
2019-05-22 16:02                                 ` Keith Busch
2019-05-22 16:35                                   ` Mario.Limonciello
2019-05-22 16:56                                     ` Keith Busch
2019-05-22 23:08                                     ` Keith Busch
2019-05-23 15:27                                       ` Keith Busch
2019-05-17  9:22                     ` Kai-Heng Feng
2019-05-17  9:32                       ` Rafael J. Wysocki
2019-05-16 20:24         ` Rafael J. Wysocki
2019-05-16  2:43 ` [PATCH 1/6] nvme-pci: Fix controller freeze wait disabling Ming Lei
2019-05-17 18:40   ` Keith Busch
2019-05-16  6:27 ` Christoph Hellwig

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=D4CDCA72-A3B8-4717-9ED2-A14254C78963@canonical.com \
    --to=kai.heng.feng@canonical.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 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.