From: Bjorn Helgaas <helgaas@kernel.org>
To: Karolina Stolarek <karolina.stolarek@oracle.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Jon Pan-Doh <pandoh@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>
Subject: Re: [PATCH] PCI/AER: Consolidate CXL and native AER reporting paths
Date: Fri, 21 Mar 2025 10:06:07 -0500 [thread overview]
Message-ID: <20250321150607.GA1124679@bhelgaas> (raw)
In-Reply-To: <457b32f0-b020-4a0a-a557-0ef8201cb6f8@oracle.com>
On Fri, Mar 21, 2025 at 02:56:16PM +0100, Karolina Stolarek wrote:
> On 20/03/2025 19:17, Bjorn Helgaas wrote:
> > Maybe there's CXL magic that I missed. It looks like Terry's series
> > changes some of this path. And GHES also currently uses
> > pci_print_aer().
> ... But still, the question is if going with the
> new format that matches what's in AER a bad or disruptive thing. I'd like to
> try going in the direction of using one way of reporting AER errors, if
> possible.
Absolutely, I agree 100%. The choice between native AER and GHES is
made by the platform, not by the OS, so I think it's crazy that we log
them differently. We just need to include information about any log
format changes we make to help users adapt to them.
Bjorn
next prev parent reply other threads:[~2025-03-21 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:14 [PATCH] PCI/AER: Consolidate CXL and native AER reporting paths Karolina Stolarek
2025-03-19 22:21 ` Bjorn Helgaas
2025-03-20 15:14 ` Karolina Stolarek
2025-03-20 18:17 ` Bjorn Helgaas
2025-03-21 13:56 ` Karolina Stolarek
2025-03-21 15:06 ` Bjorn Helgaas [this message]
2025-03-24 19:31 ` Karolina Stolarek
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=20250321150607.GA1124679@bhelgaas \
--to=helgaas@kernel.org \
--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=karolina.stolarek@oracle.com \
--cc=lenb@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