All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle
Date: Wed, 8 May 2019 13:16:24 -0600	[thread overview]
Message-ID: <20190508191624.GA8365@localhost.localdomain> (raw)
In-Reply-To: <20190508185955.11406-1-kai.heng.feng@canonical.com>

On Thu, May 09, 2019@02:59:55AM +0800, Kai-Heng Feng wrote:
> +static int nvme_do_resume_from_idle(struct pci_dev *pdev)
> +{
> +	struct nvme_dev *ndev = pci_get_drvdata(pdev);
> +	int result;
> +
> +	pdev->dev_flags &= ~PCI_DEV_FLAGS_NO_D3;
> +	ndev->ctrl.suspend_to_idle = false;
> +
> +	result = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_ALL_TYPES);
> +	if (result < 0)
> +		goto out;
> +
> +	result = nvme_pci_configure_admin_queue(ndev);
> +	if (result)
> +		goto out;
> +
> +	result = nvme_alloc_admin_tags(ndev);
> +	if (result)
> +		goto out;
> +
> +	ndev->ctrl.max_hw_sectors = NVME_MAX_KB_SZ << 1;
> +	ndev->ctrl.max_segments = NVME_MAX_SEGS;
> +	mutex_unlock(&ndev->shutdown_lock);

This lock was never locked.

But I think these special suspend/resume routines are too similar to the
existing ones, they should just incorporate this feature if we need to
do this.

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <kbusch@kernel.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: keith.busch@intel.com, axboe@fb.com, hch@lst.de,
	sagi@grimberg.me, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Mario Limonciello <mario.limonciello@dell.com>
Subject: Re: [PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle
Date: Wed, 8 May 2019 13:16:24 -0600	[thread overview]
Message-ID: <20190508191624.GA8365@localhost.localdomain> (raw)
In-Reply-To: <20190508185955.11406-1-kai.heng.feng@canonical.com>

On Thu, May 09, 2019 at 02:59:55AM +0800, Kai-Heng Feng wrote:
> +static int nvme_do_resume_from_idle(struct pci_dev *pdev)
> +{
> +	struct nvme_dev *ndev = pci_get_drvdata(pdev);
> +	int result;
> +
> +	pdev->dev_flags &= ~PCI_DEV_FLAGS_NO_D3;
> +	ndev->ctrl.suspend_to_idle = false;
> +
> +	result = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_ALL_TYPES);
> +	if (result < 0)
> +		goto out;
> +
> +	result = nvme_pci_configure_admin_queue(ndev);
> +	if (result)
> +		goto out;
> +
> +	result = nvme_alloc_admin_tags(ndev);
> +	if (result)
> +		goto out;
> +
> +	ndev->ctrl.max_hw_sectors = NVME_MAX_KB_SZ << 1;
> +	ndev->ctrl.max_segments = NVME_MAX_SEGS;
> +	mutex_unlock(&ndev->shutdown_lock);

This lock was never locked.

But I think these special suspend/resume routines are too similar to the
existing ones, they should just incorporate this feature if we need to
do this.

  parent reply	other threads:[~2019-05-08 19:16 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 18:59 [PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle Kai-Heng Feng
2019-05-08 18:59 ` Kai-Heng Feng
2019-05-08 19:15 ` Chaitanya Kulkarni
2019-05-08 19:15   ` Chaitanya Kulkarni
2019-05-08 19:16 ` Keith Busch [this message]
2019-05-08 19:16   ` Keith Busch
2019-05-08 19:30   ` Kai-Heng Feng
2019-05-08 19:30     ` Kai-Heng Feng
2019-05-08 19:38     ` Mario.Limonciello
2019-05-08 19:38       ` Mario.Limonciello
2019-05-08 19:51       ` Christoph Hellwig
2019-05-08 19:51         ` Christoph Hellwig
2019-05-08 20:28         ` Mario.Limonciello
2019-05-08 20:28           ` Mario.Limonciello
2019-05-09  6:12           ` Christoph Hellwig
2019-05-09  6:12             ` Christoph Hellwig
2019-05-09  6:48             ` Kai-Heng Feng
2019-05-09  6:48               ` Kai-Heng Feng
2019-05-09  6:52               ` Christoph Hellwig
2019-05-09  6:52                 ` Christoph Hellwig
2019-05-09  9:19                 ` Rafael J. Wysocki
2019-05-09  9:19                   ` Rafael J. Wysocki
2019-05-09  9:25                   ` Christoph Hellwig
2019-05-09  9:25                     ` Christoph Hellwig
2019-05-09  9:25                     ` Christoph Hellwig
2019-05-09 20:48                     ` Rafael J. Wysocki
2019-05-09 20:48                       ` Rafael J. Wysocki
2019-05-09  9:07               ` Rafael J. Wysocki
2019-05-09  9:07                 ` Rafael J. Wysocki
2019-05-09  9:42                 ` Kai-Heng Feng
2019-05-09  9:42                   ` Kai-Heng Feng
2019-05-09  9:56                   ` Christoph Hellwig
2019-05-09  9:56                     ` Christoph Hellwig
2019-05-09 10:28                     ` Kai-Heng Feng
2019-05-09 10:28                       ` Kai-Heng Feng
2019-05-09 10:31                       ` Christoph Hellwig
2019-05-09 10:31                         ` Christoph Hellwig
2019-05-09 11:59                         ` Kai-Heng Feng
2019-05-09 11:59                           ` Kai-Heng Feng
2019-05-09 18:57                           ` Mario.Limonciello
2019-05-09 18:57                             ` Mario.Limonciello
2019-05-09 18:57                             ` Mario.Limonciello
2019-05-09 19:28                             ` Keith Busch
2019-05-09 19:28                               ` Keith Busch
2019-05-09 20:54                               ` Rafael J. Wysocki
2019-05-09 20:54                                 ` Rafael J. Wysocki
2019-05-09 21:16                                 ` Keith Busch
2019-05-09 21:16                                   ` Keith Busch
2019-05-09 21:39                                   ` Rafael J. Wysocki
2019-05-09 21:39                                     ` Rafael J. Wysocki
2019-05-09 21:37                               ` Mario.Limonciello
2019-05-09 21:37                                 ` Mario.Limonciello
2019-05-09 21:37                                 ` Mario.Limonciello
2019-05-09 21:54                                 ` Keith Busch
2019-05-09 21:54                                   ` Keith Busch
2019-05-09 22:19                                   ` Mario.Limonciello
2019-05-09 22:19                                     ` Mario.Limonciello
2019-05-09 22:19                                     ` Mario.Limonciello
2019-05-10  6:05                                     ` Kai-Heng Feng
2019-05-10  6:05                                       ` Kai-Heng Feng
2019-05-10  8:23                                       ` Rafael J. Wysocki
2019-05-10  8:23                                         ` Rafael J. Wysocki
2019-05-10 13:52                                         ` Keith Busch
2019-05-10 13:52                                           ` Keith Busch
2019-05-10 15:15                                         ` Kai Heng Feng
2019-05-10 15:15                                           ` Kai Heng Feng
2019-05-10 15:36                                           ` Keith Busch
2019-05-10 15:36                                             ` Keith Busch
2019-05-10 14:02                                       ` Keith Busch
2019-05-10 14:02                                         ` Keith Busch
2019-05-10 15:18                                         ` Kai Heng Feng
2019-05-10 15:18                                           ` Kai Heng Feng
2019-05-10 15:49                                           ` hch
2019-05-10 15:49                                             ` hch
2019-05-10  5:30                               ` Christoph Hellwig
2019-05-10  5:30                                 ` Christoph Hellwig
2019-05-10 13:51                                 ` Keith Busch
2019-05-10 13:51                                   ` Keith Busch
2019-05-09 16:20                       ` Keith Busch
2019-05-09 16:20                         ` Keith Busch

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=20190508191624.GA8365@localhost.localdomain \
    --to=kbusch@kernel.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.