From: Xuesong Chen <xuesong.chen@linux.alibaba.com>
To: catalin.marinas@arm.com, lorenzo.pieralisi@arm.com,
james.morse@arm.com, will@kernel.org, rafael@kernel.org,
tony.luck@intel.com, bp@alien8.de, mingo@redhat.com,
bhelgaas@google.com
Cc: steve.capper@arm.com, mark.rutland@arm.com,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xuesong.chen@linux.alibaba.com
Subject: [PATCH 0/2] PCI MCFG consolidation and APEI resource filtering
Date: Wed, 6 Oct 2021 10:45:51 +0800 [thread overview]
Message-ID: <YV0N38mxpetB1pbo@Dennis-MBP.local> (raw)
The issue of commit d91525eb8ee6 ("ACPI, EINJ: Enhance error injection tolerance
level") on x86 is also happened on our own arm64 platform. We sent a patch[1]
trying to fix this issue in an arch-specific way as x86 does, but according to
the suggestion from Lorenzo and Catalin, we can consolidate the PCI MCFG part
then fix it in a more common way.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2021-September/682292.html
Xuesong Chen (2):
PCI: MCFG: Consolidate the separate PCI MCFG table entry list
ACPI: APEI: Filter the PCI MCFG address with an arch-agnostic method
arch/x86/include/asm/pci_x86.h | 17 +----------------
arch/x86/pci/mmconfig-shared.c | 30 ------------------------------
drivers/acpi/apei/apei-base.c | 42 ++++++++++++++++++++++++++----------------
drivers/acpi/pci_mcfg.c | 34 +++++++++++++---------------------
drivers/pci/pci.c | 2 ++
include/linux/pci.h | 17 +++++++++++++++++
6 files changed, 59 insertions(+), 83 deletions(-)
--
1.8.3.1
reply other threads:[~2021-10-06 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YV0N38mxpetB1pbo@Dennis-MBP.local \
--to=xuesong.chen@linux.alibaba.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=steve.capper@arm.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
/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