From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: bhelgaas@google.com, Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
linux-pm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Krzysztof Wilczyński" <kw@linux.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>
Subject: Re: [PATCH v3] PCI: vmd: Honor ACPI _OSC on PCIe features
Date: Tue, 4 Jan 2022 15:26:40 +0000 [thread overview]
Message-ID: <164130998680.26818.6364463233506760132.b4-ty@arm.com> (raw)
In-Reply-To: <20211203031541.1428904-1-kai.heng.feng@canonical.com>
On Fri, 3 Dec 2021 11:15:41 +0800, Kai-Heng Feng wrote:
> When Samsung PCIe Gen4 NVMe is connected to Intel ADL VMD, the
> combination causes AER message flood and drags the system performance
> down.
>
> The issue doesn't happen when VMD mode is disabled in BIOS, since AER
> isn't enabled by acpi_pci_root_create() . When VMD mode is enabled, AER
> is enabled regardless of _OSC:
> [ 0.410076] acpi PNP0A08:00: _OSC: platform does not support [AER]
> ...
> [ 1.486704] pcieport 10000:e0:06.0: AER: enabled with IRQ 146
>
> [...]
Applied to pci/vmd, thanks!
[1/1] PCI: vmd: Honor ACPI _OSC on PCIe features
https://git.kernel.org/lpieralisi/pci/c/04b12ef163
Thanks,
Lorenzo
prev parent reply other threads:[~2022-01-04 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 3:15 [PATCH v3] PCI: vmd: Honor ACPI _OSC on PCIe features Kai-Heng Feng
2021-12-03 14:00 ` Rafael J. Wysocki
2021-12-06 23:12 ` Keith Busch
2021-12-07 13:15 ` Rafael J. Wysocki
2022-02-09 21:36 ` Bjorn Helgaas
2022-02-10 17:52 ` Jonathan Derrick
2022-02-14 0:27 ` Kai-Heng Feng
2022-02-14 0:23 ` Kai-Heng Feng
2022-02-15 15:09 ` Bjorn Helgaas
2022-02-15 17:09 ` Rafael J. Wysocki
2022-02-16 1:53 ` Bjorn Helgaas
2022-02-16 8:14 ` Christoph Hellwig
2022-02-16 12:37 ` Rafael J. Wysocki
2022-01-04 15:26 ` Lorenzo Pieralisi [this message]
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=164130998680.26818.6364463233506760132.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=jonathan.derrick@linux.dev \
--cc=kai.heng.feng@canonical.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@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