From: Lukas Wunner <lukas@wunner.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Mario.Limonciello@dell.com,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <yehezkel.bernat@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 1/5] PCI: Make sure all bridges reserve at least one bus number
Date: Sat, 31 Mar 2018 10:29:03 +0200 [thread overview]
Message-ID: <20180331082903.GA21051@wunner.de> (raw)
In-Reply-To: <20180329115911.GN2703@lahna.fi.intel.com>
On Thu, Mar 29, 2018 at 02:59:11PM +0300, Mika Westerberg wrote:
> On Wed, Mar 28, 2018 at 01:09:06PM -0500, Bjorn Helgaas wrote:
> > The same issue could happen on any system where we use acpiphp, so I
> > don't think Thunderbolt is really relevant here, and it's easy to
> > confuse things by mentioning it.
>
> This issue can happen regardless whether acpiphp is used or not.
If the platform has yielded hotplug control to the OS via _OSC,
I don't see how the platform could hot-add devices. So surely
reserving a bus number for a bridge without anything below it
can be constrained to the !pciehp_is_native(bridge) case?
Thanks,
Lukas
next prev parent reply other threads:[~2018-03-31 8:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:21 [PATCH v3 0/5] PCI: Fixes for native PCIe and ACPI hotplug Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 1/5] PCI: Make sure all bridges reserve at least one bus number Mika Westerberg
2018-03-27 18:57 ` Bjorn Helgaas
2018-03-28 11:43 ` Mika Westerberg
2018-03-28 18:09 ` Bjorn Helgaas
2018-03-29 11:59 ` Mika Westerberg
2018-03-31 8:29 ` Lukas Wunner [this message]
2018-03-31 8:58 ` Mika Westerberg
2018-03-31 9:12 ` Lukas Wunner
2018-03-31 9:19 ` Rafael J. Wysocki
2018-03-31 9:20 ` Mika Westerberg
2018-03-31 9:30 ` Lukas Wunner
2018-03-31 9:58 ` Mika Westerberg
2018-03-31 10:18 ` Lukas Wunner
2018-03-31 10:37 ` Mika Westerberg
2018-03-31 9:30 ` Rafael J. Wysocki
2018-03-31 9:56 ` Mika Westerberg
2018-03-31 10:05 ` Rafael J. Wysocki
2018-03-31 10:12 ` Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 2/5] PCI: Take bridge window alignment into account when distributing resources Mika Westerberg
2018-03-27 19:23 ` Bjorn Helgaas
2018-03-28 12:01 ` Mika Westerberg
2018-03-29 21:29 ` Bjorn Helgaas
2018-03-31 9:18 ` Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 3/5] PCI: pciehp: Clear Presence Detect and Data Link Layer Status Changed on resume Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 4/5] ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 5/5] ACPI / hotplug / PCI: Mark stale PCI devices disconnected Mika Westerberg
2018-03-27 19:45 ` Bjorn Helgaas
2018-03-27 20:52 ` Lukas Wunner
2018-03-27 22:13 ` Bjorn Helgaas
2018-03-28 6:25 ` Greg Kroah-Hartman
2018-02-26 15:16 ` [PATCH v3 0/5] PCI: Fixes for native PCIe and ACPI hotplug Andy Shevchenko
2018-03-15 6:00 ` Mika Westerberg
2018-03-26 10:01 ` Mika Westerberg
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=20180331082903.GA21051@wunner.de \
--to=lukas@wunner.de \
--cc=Mario.Limonciello@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=yehezkel.bernat@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).