From: sashiko-bot@kernel.org
To: "Guixin Liu" <kanie@linux.alibaba.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 1/2] PCI/bwctrl: Add pci_bwctrl_available()
Date: Wed, 29 Jul 2026 03:52:31 +0000 [thread overview]
Message-ID: <20260729035231.AF0841F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729034505.469107-2-kanie@linux.alibaba.com>
> Enabling the PCIe bandwidth controller sets the Link Bandwidth Management
> Interrupt Enable (LBMIE) and Link Autonomous Bandwidth Interrupt Enable
> (LABIE) bits. On some (typically old) platforms this has been observed to
> cause boot hangs, e.g. commit 46a9f70e93ef ("PCI/bwctrl: Disable BW
> controller on Intel P45 using a quirk") works around one such case with a
> per-device quirk.
>
> In preparation for a system-wide switch to turn the bandwidth controller
> off, add pci_bwctrl_available() and pci_no_bwctrl(), mirroring
> pci_aer_available()/pci_no_aer(), and consult the former when deciding
> whether to enable PCIE_PORT_SERVICE_BWCTRL.
>
> No functional change intended: the controller stays available by default.
>
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729034505.469107-1-kanie@linux.alibaba.com?part=1
next prev parent reply other threads:[~2026-07-29 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 3:45 [PATCH v1 0/2] PCI: Add pci=nobwctrl to disable the PCIe bandwidth controller Guixin Liu
2026-07-29 3:45 ` [PATCH v1 1/2] PCI/bwctrl: Add pci_bwctrl_available() Guixin Liu
2026-07-29 3:52 ` sashiko-bot [this message]
2026-07-29 3:45 ` [PATCH v1 2/2] PCI: Add pci=nobwctrl parameter to disable the PCIe bandwidth controller Guixin Liu
2026-07-29 3:50 ` sashiko-bot
2026-07-29 7:01 ` [PATCH v1 0/2] PCI: Add pci=nobwctrl " Lukas Wunner
2026-07-29 8:28 ` Guixin Liu
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=20260729035231.AF0841F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kanie@linux.alibaba.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.