From: Sinan Kaya <okaya@kernel.org>
To: Ethan Zhao <haifeng.zhao@intel.com>,
bhelgaas@google.com, oohall@gmail.com, ruscur@russell.cc,
lukas@wunner.de, andriy.shevchenko@linux.intel.com,
stuart.w.hayes@gmail.com, mr.nuke.me@gmail.com,
mika.westerberg@linux.intel.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
ashok.raj@linux.intel.com, sathyanarayanan.kuppuswamy@intel.com,
xerces.zhao@gmail.com
Subject: Re: [PATCH v6 4/5] PCI: only return true when dev io state is really changed
Date: Fri, 2 Oct 2020 12:08:27 -0400 [thread overview]
Message-ID: <52e9ba48-2789-31b8-b80c-23854190c4d4@kernel.org> (raw)
In-Reply-To: <20200930070537.30982-5-haifeng.zhao@intel.com>
On 9/30/2020 3:05 AM, Ethan Zhao wrote:
> When uncorrectable error happens, AER driver and DPC driver interrupt
> handlers likely call
>
> pcie_do_recovery()
> ->pci_walk_bus()
> ->report_frozen_detected()
>
> with pci_channel_io_frozen the same time.
We need some more data on this. If DPC is supported by HW, errors
should be triggered by DPC not AER.
If I remember right, there is a register that tells which AER errors
should be handled by DPC.
next prev parent reply other threads:[~2020-10-02 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:05 [PATCH v6 0/5] Fix DPC hotplug race and enhance error handling Ethan Zhao
2020-09-30 7:05 ` [PATCH v6 1/5] PCI/ERR: get device before call device driver to avoid NULL pointer dereference Ethan Zhao
2020-09-30 7:05 ` [PATCH v6 2/5] PCI/DPC: define a function to check and wait till port finish DPC handling Ethan Zhao
2020-09-30 7:05 ` [PATCH v6 3/5] PCI: pciehp: check and wait port status out of DPC before handling DLLSC and PDC Ethan Zhao
2020-09-30 7:05 ` [PATCH v6 4/5] PCI: only return true when dev io state is really changed Ethan Zhao
2020-10-02 16:08 ` Sinan Kaya [this message]
2020-10-03 5:46 ` Ethan Zhao
2020-10-02 17:29 ` Bjorn Helgaas
2020-10-03 7:05 ` Ethan Zhao
2020-09-30 7:05 ` [PATCH v6 5/5] PCI/ERR: don't mix io state not changed and no driver together Ethan Zhao
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=52e9ba48-2789-31b8-b80c-23854190c4d4@kernel.org \
--to=okaya@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ashok.raj@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=haifeng.zhao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=mr.nuke.me@gmail.com \
--cc=oohall@gmail.com \
--cc=ruscur@russell.cc \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=stuart.w.hayes@gmail.com \
--cc=xerces.zhao@gmail.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