From: LeoLiuoc <LeoLiu-oc@zhaoxin.com>
To: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>, <rafael@kernel.org>,
<lenb@kernel.org>, <james.morse@arm.com>, <tony.luck@intel.com>,
<bp@alien8.de>, <robert.moore@intel.com>, <ying.huang@intel.com>,
<rdunlap@infradead.org>, <bhelgaas@google.com>,
<linux-acpi@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devel@acpica.org>
Cc: <CobeChen@zhaoxin.com>, <TonyWWang@zhaoxin.com>, <ErosZhang@zhaoxin.com>
Subject: Re: [PATCH 0/5] Parse the PCIE AER structure and set to relevant registers
Date: Fri, 28 Oct 2022 19:19:25 +0800 [thread overview]
Message-ID: <d4096cf3-7f16-b20c-01ea-e235bc90ae77@zhaoxin.com> (raw)
In-Reply-To: <a0f29483-9557-9900-bcb7-ec832dc5d2d1@linux.intel.com>
在 2022/10/27 12:17, Sathyanarayanan Kuppuswamy 写道:
>
>
> On 10/26/22 8:14 PM, LeoLiu-oc wrote:
>> From: leoliu-oc <leoliu-oc@zhaoxin.com>
>>
>> HEST PCIE AER error source information describes the Uncorrectable Error
>> Severity, CorrectableError Mask and other aer register's value to write to the
>
> /s/CorrectableError/Correctable Error
> /s/aer/AER
Got it. I will modify this in next version patch set.
Thanks
leoliu-oc
>
>> bridge's Correctable Error Mask register.
>
> Can you add spec reference?
>
Please refer to Section 18.3.2 ACPI Error Source of acpi spec v6.3.
Links to the online versions of ACPI Spec 6.3 is
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/18_ACPI_Platform_Error_Interfaces/error-source-discovery.html#acpi-error-source.
Section 18.3.2.4 describes PCI Express Root Port AER Structure, section
18.3.2.5 describes PCI Express Device AER Structure, section 18.3.2.6
describes PCI Express/PCI-X Bridge AER Structure.
Thanks
leoliu-oc
>>
>> leoliu-oc (5):
>> ACPI/APEI: Add apei_hest_parse_aer()
>> ACPI/APEI: remove static from apei_hest_parse()
>> ACPI/PCI: Add AER bits #defines for PCIE/PCI-X bridges
>> ACPI/PCI: Add pci_acpi_program_hest_aer_params()
>> ACPI/PCI: config pcie devices's aer register
>>
>> drivers/acpi/apei/hest.c | 121 +++++++++++++++++++++++++++++++++-
>> drivers/pci/pci-acpi.c | 92 ++++++++++++++++++++++++++
>> drivers/pci/pci.h | 5 ++
>> drivers/pci/probe.c | 1 +
>> include/acpi/actbl1.h | 69 +++++++++++++++++++
>> include/acpi/apei.h | 9 +++
>> include/uapi/linux/pci_regs.h | 5 ++
>> 7 files changed, 300 insertions(+), 2 deletions(-)
>>
>
next prev parent reply other threads:[~2022-10-28 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 3:14 [PATCH 0/5] Parse the PCIE AER structure and set to relevant registers LeoLiu-oc
2022-10-27 4:17 ` Sathyanarayanan Kuppuswamy
2022-10-28 11:19 ` LeoLiuoc [this message]
2022-10-28 15:15 ` Bjorn Helgaas
2022-11-01 7:25 ` LeoLiuoc
2022-10-27 22:09 ` Bjorn Helgaas
2022-10-28 11:23 ` LeoLiuoc
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=d4096cf3-7f16-b20c-01ea-e235bc90ae77@zhaoxin.com \
--to=leoliu-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=ErosZhang@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=devel@acpica.org \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robert.moore@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.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