From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Puranjay Mohan <puranjay12@gmail.com>,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/7] PCI: Improve enumeration logging
Date: Tue, 5 Dec 2023 11:11:12 -0600 [thread overview]
Message-ID: <20231205171119.680358-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
This is based on Puranjay Mohan's work at
https://lore.kernel.org/all/20211106112606.192563-1-puranjay12@gmail.com/
which updated BAR resource logging to consistently use "BAR 0" instead of a
mix of "BAR 0", "reg 0x10", etc.
I added:
- More BAR resource log updates
- Device type (PCIe Root Port, Switch Port, etc) to initial message
- Bridge info logging in logical order (bridge before downstream)
Bjorn Helgaas (5):
PCI: Log device type during enumeration
PCI: Move pci_read_bridge_windows() below individual window accessors
PCI: Supply bridge device, not secondary bus, to read window details
PCI: Log bridge windows conditionally
PCI: Log bridge info when first enumerating bridge
Puranjay Mohan (2):
PCI: Update BAR # and window messages
PCI: Use resource names in PCI log messages
drivers/pci/iov.c | 7 +-
drivers/pci/pci.c | 85 ++++++++++++++--
drivers/pci/pci.h | 2 +
drivers/pci/probe.c | 218 ++++++++++++++++++++++++----------------
drivers/pci/quirks.c | 15 ++-
drivers/pci/setup-bus.c | 30 ++++--
drivers/pci/setup-res.c | 72 +++++++------
7 files changed, 286 insertions(+), 143 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-05 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 17:11 Bjorn Helgaas [this message]
2023-12-05 17:11 ` [PATCH 1/7] PCI: Log device type during enumeration Bjorn Helgaas
2023-12-06 0:31 ` Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 2/7] PCI: Update BAR # and window messages Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 3/7] PCI: Use resource names in PCI log messages Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 4/7] PCI: Move pci_read_bridge_windows() below individual window accessors Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 5/7] PCI: Supply bridge device, not secondary bus, to read window details Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 6/7] PCI: Log bridge windows conditionally Bjorn Helgaas
2023-12-05 17:11 ` [PATCH 7/7] PCI: Log bridge info when first enumerating bridge Bjorn Helgaas
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=20231205171119.680358-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=puranjay12@gmail.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