From: Lukas Wunner <lukas@wunner.de>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, kbusch@kernel.org,
sathyanarayanan.kuppuswamy@linux.intel.com, mahesh@linux.ibm.com,
oohall@gmail.com, Jonathan.Cameron@huawei.com,
terry.bowman@amd.com, tianruidong@linux.alibaba.com
Subject: Re: [PATCH v6 4/5] PCI/ERR: Use pcie_aer_is_native() to check for native AER control
Date: Fri, 24 Oct 2025 06:03:00 +0200 [thread overview]
Message-ID: <aPr6dBDUUohRUzYg@wunner.de> (raw)
In-Reply-To: <91cf33b4-7f67-4f3a-b095-e8f04d8c18e9@linux.alibaba.com>
On Fri, Oct 24, 2025 at 11:38:10AM +0800, Shuai Xue wrote:
> The remaining question is whether it would make more sense to rename
> pcie_clear_device_status() to pci_clear_device_error_status() and refine
> its behavior by adding a mask specifically for bits 0 to 3. Here's an
> example of the proposed change:
I don't see much value in renaming the function.
However clearing only bits 0-3 makes sense. PCIe r5.0 defined bit 6
as Emergency Power Reduction Detected with type RW1C in 2019. The
last time we touched pcie_clear_device_status() was in 2018 with
ec752f5d54d7 and we've been clearing all bits since forever,
not foreseeing that new ones with type RW1C might be added later.
I suggest defining a new macro in include/uapi/linux/pci_regs.h
instead of using 0xf, say PCI_EXP_DEVSTA_ERR. Then you don't
need the code comment because the code is self-explanatory.
Thanks,
Lukas
next prev parent reply other threads:[~2025-10-24 4:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:41 [PATCH v6 0/5] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-10-15 2:41 ` [PATCH v6 1/5] PCI/DPC: Clarify naming for error port in DPC Handling Shuai Xue
2025-10-15 2:41 ` [PATCH v6 2/5] PCI/DPC: Run recovery on device that detected the error Shuai Xue
2025-10-15 2:41 ` [PATCH v6 3/5] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-10-20 10:10 ` Lukas Wunner
2025-10-20 12:58 ` Shuai Xue
2025-10-20 13:54 ` Lukas Wunner
2025-10-20 14:17 ` Shuai Xue
2025-10-20 14:24 ` Lukas Wunner
2025-10-20 15:20 ` Shuai Xue
2025-10-23 10:48 ` Lukas Wunner
2025-10-24 6:43 ` Shuai Xue
2025-12-16 8:07 ` Shuai Xue
2025-10-20 18:38 ` Kuppuswamy Sathyanarayanan
2025-10-21 1:51 ` Shuai Xue
2025-10-15 2:41 ` [PATCH v6 4/5] PCI/ERR: Use pcie_aer_is_native() to check for native AER control Shuai Xue
2025-10-20 10:17 ` Lukas Wunner
2025-10-20 13:09 ` Shuai Xue
2025-10-20 13:58 ` Lukas Wunner
2025-10-20 14:45 ` Shuai Xue
2025-10-23 10:29 ` Lukas Wunner
2025-10-24 3:09 ` Shuai Xue
2025-10-24 3:14 ` Lukas Wunner
2025-10-24 3:38 ` Shuai Xue
2025-10-24 4:03 ` Lukas Wunner [this message]
2025-10-24 5:37 ` Shuai Xue
2025-10-20 18:43 ` Kuppuswamy Sathyanarayanan
2025-10-15 2:41 ` [PATCH v6 5/5] PCI/AER: Clear both AER fatal and non-fatal status Shuai Xue
2025-10-20 18:44 ` Kuppuswamy Sathyanarayanan
2025-10-21 1:33 ` Shuai Xue
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=aPr6dBDUUohRUzYg@wunner.de \
--to=lukas@wunner.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=terry.bowman@amd.com \
--cc=tianruidong@linux.alibaba.com \
--cc=xueshuai@linux.alibaba.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.