From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
To: Lukas Wunner <lukas@wunner.de>,
"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Bhat, Jay" <jay.bhat@intel.com>,
"Barrera, Ivan D" <ivan.d.barrera@intel.com>,
"Zaremba, Larysa" <larysa.zaremba@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Chittim, Madhu" <madhu.chittim@intel.com>,
"decot@google.com" <decot@google.com>,
"willemb@google.com" <willemb@google.com>,
"sheenamo@google.com" <sheenamo@google.com>
Subject: Re: [PATCH iwl-next v2 2/2] idpf: implement pci error handlers
Date: Tue, 14 Apr 2026 14:42:50 -0700 [thread overview]
Message-ID: <904b95de-491b-41c1-b092-0da56ad4c349@intel.com> (raw)
In-Reply-To: <ad5Y-gNBDvns-WAE@wunner.de>
On 4/14/2026 8:10 AM, Lukas Wunner wrote:
> On Tue, Apr 14, 2026 at 11:09:05AM +0000, Loktionov, Aleksandr wrote:
>>> From: Tantilov, Emil S <emil.s.tantilov@intel.com>
>>> .slot_reset is the callback attempting to restore the device, provided
>>> a PCI reset was initiated by the AER driver.
>
> Just for clarity, those callbacks are invoked by PCI core error handling
> code and are shared by EEH, AER, DPC as well as s390 error recovery flows.
> So it's not only AER.
Understood. I can change the wording to be more generic.
>
>>> +/**
>>> + * idpf_pci_err_resume - Resume operations after PCI error recovery
>>> + * @pdev: PCI device struct
>>> + */
>>> +static void idpf_pci_err_resume(struct pci_dev *pdev) {
>>> + struct idpf_adapter *adapter = pci_get_drvdata(pdev);
>>> +
>>> + /* Force a PFR when resuming from PCI error. */
>>> + if (test_and_set_bit(IDPF_PCI_CB_RESET, adapter->flags))
>>> + adapter->dev_ops.reg_ops.trigger_reset(adapter,
>>> IDPF_HR_FUNC_RESET);
>>
>> You say "Force a PFR", but PFR is only triggered on the AER path,
>> not on the FLR path.
>
> And? idpf_pci_err_resume() is only invoked in the error recovery path
> (aka AER path), not FLR path AFAICS.
The driver calls is in idpf_pci_err_reset_done():
<...>-86378 [009] ..... 342752.746321: idpf_pci_err_reset_prepare
<-pci_dev_save_and_disable
bash-86378 [045] ..... 342756.748148: idpf_pci_err_reset_done
<-pci_reset_function
bash-86378 [045] ..... 342756.748272: idpf_pci_err_resume
<-pci_reset_function
Thanks,
Emil
>
> Thanks,
>
> Lukas
next prev parent reply other threads:[~2026-04-14 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 3:16 [PATCH iwl-next v2 0/2] Introduce IDPF PCI callbacks Emil Tantilov
2026-04-14 3:16 ` [PATCH iwl-next v2 1/2] idpf: remove conditonal MBX deinit from idpf_vc_core_deinit() Emil Tantilov
2026-04-14 11:07 ` Loktionov, Aleksandr
2026-04-14 14:56 ` Tantilov, Emil S
2026-04-14 3:16 ` [PATCH iwl-next v2 2/2] idpf: implement pci error handlers Emil Tantilov
2026-04-14 11:09 ` Loktionov, Aleksandr
2026-04-14 15:01 ` Tantilov, Emil S
2026-04-15 8:53 ` Loktionov, Aleksandr
2026-04-14 15:10 ` Lukas Wunner
2026-04-14 21:42 ` Tantilov, Emil S [this message]
2026-04-14 15:13 ` Lukas Wunner
2026-04-14 21:43 ` Tantilov, Emil S
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=904b95de-491b-41c1-b092-0da56ad4c349@intel.com \
--to=emil.s.tantilov@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivan.d.barrera@intel.com \
--cc=jay.bhat@intel.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sheenamo@google.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox