From: Bjorn Helgaas <helgaas@kernel.org>
To: Blazej Kucman <blazej.kucman@linux.intel.com>
Cc: Nirmal Patel <nirmal.patel@linux.intel.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
linux-pci@vger.kernel.org,
Blazej Kucman <blazej.kucman@intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Lukas Wunner <lukas@wunner.de>,
Naveen Naidu <naveennaidu479@gmail.com>,
Keith Busch <kbusch@kernel.org>,
Jonathan Derrick <jonathan.derrick@linux.dev>
Subject: Re: [Bug 215525] New: HotPlug does not work on upstream kernel 5.17.0-rc1
Date: Wed, 9 Feb 2022 15:02:18 -0600 [thread overview]
Message-ID: <20220209210218.GA587489@bhelgaas> (raw)
In-Reply-To: <20220209144102.0000143e@linux.intel.com>
On Wed, Feb 09, 2022 at 02:41:02PM +0100, Blazej Kucman wrote:
> On Thu, 3 Feb 2022 09:58:04 -0600
> Bjorn Helgaas <helgaas@kernel.org> wrote:
> > Why were you testing with "pci=nommconf"? Do you think anybody uses
> > that with VMD and NVMe?
>
> It was added long time ago when it was useful.
I'm curious about why it was useful. It suggests a possible MMCONFIG
issue in firmware or in Linux. If it was a Linux issue, ideally we
would fix that. If it's a firmware issue, ideally we would work
around it or automatically turn on "pci=nommconf" so the user wouldn't
have to figure that out.
> Bugzilla report can be closed if you don't consider it as regression.
OK, I closed it with the details. I'm not entirely convinced that
04b12ef163d1 ("PCI: vmd: Honor ACPI _OSC on PCIe features") was the
right thing, but I'll pursue that elsewhere.
Thanks for your patience in working through this, and sorry for the
hassle it caused you.
Bjorn
next prev parent reply other threads:[~2022-02-09 21:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215525-41252@https.bugzilla.kernel.org/>
2022-01-24 21:46 ` [Bug 215525] New: HotPlug does not work on upstream kernel 5.17.0-rc1 Bjorn Helgaas
2022-01-25 8:58 ` Hans de Goede
2022-01-25 15:33 ` Lukas Wunner
2022-01-26 7:31 ` Thorsten Leemhuis
2022-01-27 14:46 ` Mariusz Tkaczyk
2022-01-27 20:47 ` Jonathan Derrick
2022-01-27 22:31 ` Jonathan Derrick
2022-01-28 2:52 ` Bjorn Helgaas
2022-01-28 8:29 ` Mariusz Tkaczyk
2022-01-28 13:08 ` Bjorn Helgaas
2022-01-28 13:49 ` Kai-Heng Feng
2022-01-28 14:03 ` Bjorn Helgaas
2022-02-02 15:48 ` Blazej Kucman
2022-02-02 16:43 ` Bjorn Helgaas
2022-02-03 9:13 ` Thorsten Leemhuis
2022-02-03 10:47 ` Blazej Kucman
2022-02-03 15:58 ` Bjorn Helgaas
2022-02-09 13:41 ` Blazej Kucman
2022-02-09 21:02 ` Bjorn Helgaas [this message]
2022-02-10 11:14 ` Blazej Kucman
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=20220209210218.GA587489@bhelgaas \
--to=helgaas@kernel.org \
--cc=blazej.kucman@intel.com \
--cc=blazej.kucman@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jonathan.derrick@linux.dev \
--cc=kai.heng.feng@canonical.com \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=naveennaidu479@gmail.com \
--cc=nirmal.patel@linux.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).