From: Raag Jadav <raag.jadav@intel.com>
To: rafael@kernel.org, mahesh@linux.ibm.com, oohall@gmail.com,
bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, lukas@wunner.de,
aravind.iddamsetty@linux.intel.com
Subject: Re: [PATCH v3] PCI: Prevent power state transition of erroneous device
Date: Mon, 12 May 2025 13:23:47 +0300 [thread overview]
Message-ID: <aCHMM7YMqT8onaKl@black.fi.intel.com> (raw)
In-Reply-To: <20250504090444.3347952-1-raag.jadav@intel.com>
On Sun, May 04, 2025 at 02:34:44PM +0530, Raag Jadav wrote:
> If error flags are set on an AER capable device, most likely either the
> device recovery is in progress or has already failed. Neither of the
> cases are well suited for power state transition of the device, since
> this can lead to unpredictable consequences like resume failure, or in
> worst case the device is lost because of it. Leave the device in its
> existing power state to avoid such issues.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
>
> v2: Synchronize AER handling with PCI PM (Rafael)
> v3: Move pci_aer_in_progress() to pci_set_low_power_state() (Rafael)
> Elaborate "why" (Bjorn)
>
> More discussion on [1].
> [1] https://lore.kernel.org/all/CAJZ5v0g-aJXfVH+Uc=9eRPuW08t-6PwzdyMXsC6FZRKYJtY03Q@mail.gmail.com/
Bump. Anything I can do to move this forward?
Raag
next prev parent reply other threads:[~2025-05-12 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 9:04 Raag Jadav
2025-05-12 10:23 ` Raag Jadav [this message]
2025-05-12 11:56 ` Rafael J. Wysocki
2025-05-12 16:52 ` Raag Jadav
2025-05-13 4:41 ` Lukas Wunner
2025-05-13 15:17 ` Raag Jadav
2025-05-14 16:29 ` Denis Benato
2025-05-14 19:53 ` Mario Limonciello
2025-05-14 21:25 ` Denis Benato
2025-05-15 11:58 ` Raag Jadav
2025-05-15 12:26 ` Lukas Wunner
2025-05-15 14:11 ` Denis Benato
2025-05-15 14:41 ` Mario Limonciello
2025-05-21 13:33 ` Lukas Wunner
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=aCHMM7YMqT8onaKl@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®