From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>
Subject: Re: [PATCH] PCI/AER: Block runtime suspend when handling errors
Date: Mon, 12 Feb 2024 09:13:06 +0100 [thread overview]
Message-ID: <ZcnSgGBjpH3w9ZJa@linux.intel.com> (raw)
In-Reply-To: <64ad8d52-ba67-4156-8e36-7346605bdf48@linux.intel.com>
On Fri, Feb 09, 2024 at 07:45:05AM -0800, Kuppuswamy Sathyanarayanan wrote:
>
> On 2/9/24 6:08 AM, Stanislaw Gruszka wrote:
> > PM runtime can be done simultaneously with AER error handling.
> > Avoid that by using pm_runtime_get_sync() before and pm_runtime_put()
> > after reset in pcie_do_recovery() for all recovering devices.
> >
> > pm_runtime_get_sync() will increase dev->power.usage_count counter
> > to prevent any possible future request to runtime suspend a device,
> > as well as resume device is was in D3hot state.
> runtime suspend a device or resume a device that was in D3hot state.
I think "or" is not proper here, since both: resume and prevention
of suspend are done. I'll reword this way:
pm_runtime_get_sync() will increase dev->power.usage_count counter
to prevent any possible future request to runtime suspend a device
It will also resume a device, if it was previously in D3hot state.
Hope that's clearer.
Thanks
Stanislaw
prev parent reply other threads:[~2024-02-12 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 14:08 [PATCH] PCI/AER: Block runtime suspend when handling errors Stanislaw Gruszka
2024-02-09 14:16 ` Rafael J. Wysocki
2024-02-09 15:45 ` Kuppuswamy Sathyanarayanan
2024-02-12 8:13 ` Stanislaw Gruszka [this message]
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=ZcnSgGBjpH3w9ZJa@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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.