From: Bjorn Helgaas <helgaas@kernel.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Nirmal Patel <nirmal.patel@linux.intel.com>,
linux-pci@vger.kernel.org, orden.e.smith@intel.com,
samruddh.dhope@intel.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Grant Grundler <grundler@chromium.org>,
Rajat Khandelwal <rajat.khandelwal@linux.intel.com>,
Rajat Jain <rajatja@chromium.org>
Subject: Re: [PATCH] PCI: vmd: Enable Hotplug based on BIOS setting on VMD rootports
Date: Wed, 6 Dec 2023 10:30:26 -0600 [thread overview]
Message-ID: <20231206163026.GA716688@bhelgaas> (raw)
In-Reply-To: <CAAd53p5+x44XLLXYDKceZrgO0z-bCbFPqwR1Qw6Esjv+dUjh2w@mail.gmail.com>
[+cc Grant, Rajat, Rajat]
On Wed, Dec 06, 2023 at 10:18:56AM +0800, Kai-Heng Feng wrote:
> On Wed, Nov 15, 2023 at 5:00 AM Nirmal Patel <nirmal.patel@linux.intel.com> wrote:
> > On Wed, 2023-11-08 at 16:49 +0200, Kai-Heng Feng wrote:
> > > On Wed, Nov 8, 2023 at 12:30 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
> ...
> > > > I assume you mean to revert 04b12ef163d1 ("PCI: vmd: Honor
> > > > ACPI _OSC on PCIe features"). That appeared in v5.17, and it
> > > > fixed (or at least prevented) an AER message flood. We can't
> > > > simply revert 04b12ef163d1 unless we first prevent that AER
> > > > message flood in another way.
> > >
> > > The error is "correctable". Does masking all correctable AER
> > > error by default make any sense? And add a sysfs knob to make it
> > > optional.
> >
> > I assume sysfs knob requires driver reload. right? Can you send a
> > patch?
>
> What I mean is to mask Correctable Errors by default on *all*
> rootports, and create a new sysfs knob to let user decide if
> Correctable Errors should be unmasked.
I don't think we should mask Correctable Errors by default. Even
though they've been corrected by hardware and no software action is
required, I think these errors are valuable signals about Link
integrity.
I think rate-limiting and/or reporting on the *frequency* of
Correctable Errors would make a lot of sense. We had some work toward
this recently, but it hasn't quite gotten finished yet.
The most recent work I'm aware of is this:
https://lore.kernel.org/r/20230606035442.2886343-1-grundler@chromium.org
Bjorn
next prev parent reply other threads:[~2023-12-06 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 20:16 [PATCH] PCI: vmd: Enable Hotplug based on BIOS setting on VMD rootports Nirmal Patel
2023-10-31 15:31 ` Bjorn Helgaas
2023-10-31 19:59 ` Nirmal Patel
2023-10-31 23:26 ` Nirmal Patel
2023-11-01 22:20 ` Bjorn Helgaas
2023-11-02 20:07 ` Nirmal Patel
2023-11-02 20:41 ` Bjorn Helgaas
2023-11-02 23:49 ` Nirmal Patel
2023-11-07 21:50 ` Nirmal Patel
2023-11-07 22:30 ` Bjorn Helgaas
2023-11-08 14:49 ` Kai-Heng Feng
2023-11-08 19:44 ` Nirmal Patel
2023-11-14 21:07 ` Nirmal Patel
2023-12-06 2:18 ` Kai-Heng Feng
2023-12-06 16:30 ` Bjorn Helgaas [this message]
2023-12-11 23:19 ` Nirmal Patel
2023-12-12 3:20 ` Kai-Heng Feng
2023-11-14 23:29 ` Nirmal Patel
2023-10-31 20:11 ` Nirmal Patel
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=20231206163026.GA716688@bhelgaas \
--to=helgaas@kernel.org \
--cc=grundler@chromium.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=orden.e.smith@intel.com \
--cc=rajat.khandelwal@linux.intel.com \
--cc=rajatja@chromium.org \
--cc=rjw@rjwysocki.net \
--cc=samruddh.dhope@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;
as well as URLs for NNTP newsgroup(s).