From: Karolina Stolarek <karolina.stolarek@oracle.com>
To: Jon Pan-Doh <pandoh@google.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Terry Bowman <terry.bowman@amd.com>, Len Brown <lenb@kernel.org>,
James Morse <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Ben Cheatham <Benjamin.Cheatham@amd.com>,
Ira Weiny <ira.weiny@intel.com>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Liu Xinpeng <liuxp11@chinatelecom.cn>,
Darren Hart <darren@os.amperecomputing.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI/AER: Consolidate CXL, ACPI GHES and native AER reporting paths
Date: Fri, 4 Apr 2025 11:33:19 +0200 [thread overview]
Message-ID: <fed73e8a-5d4f-4478-bf8c-c93a7e5fd1f1@oracle.com> (raw)
In-Reply-To: <CAMC_AXXPKsat846r==J_OYQA2j8kT-kZriuSqoH3F_nYEN8ATg@mail.gmail.com>
On 01/04/2025 03:47, Jon Pan-Doh wrote:
> On Tue, Mar 25, 2025 at 8:08 AM Karolina Stolarek
> <karolina.stolarek@oracle.com> wrote:
>>
>> +static void populate_aer_err_info(struct aer_err_info *info, int severity,
>> + struct aer_capability_regs *aer_regs)
>> {
>> [...]
>> + if (severity == AER_CORRECTABLE) {
>> + info->id = aer_regs->cor_err_source;
>> + info->status = aer_regs->cor_status;
>> + info->mask = aer_regs->cor_mask;
>> + } else {
>> + info->id = aer_regs->uncor_err_source;
>
> info->id isn't filled in pci_print_aer(). Is the addition due to
> aer_print_error() having a conditional/log for info->id == id? From a
> brief look at the code, FW-first (e.g. errors from GHES), I think it
> will always be true. However, that doesn't always seem to be the case
> for CXL (e.g. when cxl_dev_state.rcd == true).
I just went with what aer_print_error() expected to get from the
aer_err_info struct. It's possible that this id check is not be needed
for GHES, but I thought that as the values are already in the regs, it
wouldn't hurt to extract them.
>
> Disclaimer: not a CXL/GHES expert though.
>
>> +void aer_print_platform_error(struct pci_dev *pdev, int severity,
>> + struct aer_capability_regs *aer_regs)
>
> I like the encapsulation.
>
> Reviewed-by: Jon Pan-Doh <pandoh@google.com>
Thanks a lot!
All the best,
Karolina
>
> Thanks,
> Jon
next prev parent reply other threads:[~2025-04-04 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 15:07 [PATCH v2] PCI/AER: Consolidate CXL, ACPI GHES and native AER reporting paths Karolina Stolarek
2025-04-01 1:47 ` Jon Pan-Doh
2025-04-04 9:33 ` Karolina Stolarek [this message]
2025-04-23 13:52 ` Karolina Stolarek
2025-04-23 20:31 ` Bjorn Helgaas
2025-04-24 9:01 ` Karolina Stolarek
2025-04-24 17:28 ` Bjorn Helgaas
2025-04-25 10:32 ` Karolina Stolarek
2025-04-25 13:14 ` Jonathan Cameron
2025-04-25 14:12 ` Karolina Stolarek
2025-04-29 15:54 ` Jonathan Cameron
2025-05-05 9:58 ` Karolina Stolarek
2025-05-05 17:45 ` Bjorn Helgaas
2025-05-06 17:03 ` Jonathan Cameron
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=fed73e8a-5d4f-4478-bf8c-c93a7e5fd1f1@oracle.com \
--to=karolina.stolarek@oracle.com \
--cc=Benjamin.Cheatham@amd.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=darren@os.amperecomputing.com \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuxp11@chinatelecom.cn \
--cc=pandoh@google.com \
--cc=terry.bowman@amd.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox