Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nikolas Joshua Britton" <nbritton@exabit.io>
Cc: linux-pci@vger.kernel.org
Subject: Re: PCI: bridge window undersized when child bridge windows are larger than their alignment (regression since 3958bf16e2fe, v7.0)
Date: Thu, 03 Sep 2026 06:41:14 +0000	[thread overview]
Message-ID: <20260903064115.062EB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260903063124.9316-1-nbritton@exabit.io>

> Hi,
> 
> On a Mac Pro 7,1 with two Radeon Pro Vega II Duo cards, enabling 32 GB
> Resizable BARs leaves exactly half the GPU dies with no BAR at all. The
> shared root-port prefetchable window is sized as the plain sum of its two
> child bridge windows, but each child secretly requires a 32 GB-aligned
> start, so the window that gets allocated is ~32 GB smaller than the span
> that is actually needed. The second child of each pair loses,
> deterministically.
> 
> There is 1 TiB of free space in the host bridge's _CRS window, so this is
> not address-space exhaustion.
> 
> This is a regression. On the same machine, with the same script
> (resize-amdgpu-bars, https://github.com/exabit-io/resize-amdgpu-bars,
> [ ... ]
>   - lspci -vvnn from the v7.0.12 + patch boot
> 
> 
> #regzbot introduced: 3958bf16e2fe
> 

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260903063124.9316-1-nbritton@exabit.io?part=1


  reply	other threads:[~2026-09-03  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  6:31 PCI: bridge window undersized when child bridge windows are larger than their alignment (regression since 3958bf16e2fe, v7.0) Nikolas Joshua Britton
2026-09-03  6:41 ` sashiko-bot [this message]
2026-09-03 11:46 ` Ilpo Järvinen

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=20260903064115.062EB1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nbritton@exabit.io \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox