linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: "Christian König" <christian.koenig@amd.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, jon@solid-run.com, wasim.khan@nxp.com
Subject: Re: [PATCH] PCI: allow pci_resize_resource() to be used on devices on the root bus
Date: Sat, 25 Apr 2020 19:32:07 +0200	[thread overview]
Message-ID: <CAMj1kXH3WVMehgbMwUEjBSYudAM7PtWAcAYcWspyq4eZJzBwTQ@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXE0wFtyD7YGxXzKWAx+BT6x9CYreaFyEeFfeYJFeQbo_g@mail.gmail.com>

On Tue, 21 Apr 2020 at 19:07, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Tue, 21 Apr 2020 at 18:43, Christian König <christian.koenig@amd.com> wrote:
> >
> > Am 21.04.20 um 18:22 schrieb Ard Biesheuvel:
> > > When resizing a BAR, pci_reassign_bridge_resources() is invoked to
> > > bring the bridge windows of parent bridges in line with the new BAR
> > > assignment.
> > >
> > > This assumes that the device whose BAR is being resized lives on a
> > > subordinate bus, but this is not necessarily the case. A device may
> > > live on the root bus, in which case dev->bus->self is NULL, and
> > > passing a NULL pci_dev pointer to pci_reassign_bridge_resources()
> > > will cause it to crash.
> > >
> > > So let's make the call to pci_reassign_bridge_resources() conditional
> > > on whether dev->bus->self is non-NULL in the first place.
> > >
> > > Fixes: 8bb705e3e79d84e7 ("PCI: Add pci_resize_resource() for resizing BARs")
> > > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> >
> > Sounds like it makes sense, patch is
> > Reviewed-by: Christian König <christian.koenig@amd.com>.
>
> Thanks Christian.
>
> >
> > May I ask where you found that condition?
> >
>
> In this particular case, it was on an ARM board with funky PCIe IP
> that does not expose a root port in its bus hierarchy.
>
> But in the general case, PCIe endpoints can be integrated into the
> root complex, in which case they appear on the root bus, and there is
> no reason such endpoints shouldn't be allowed to have resizable BARs.

Actually, looking at this more carefully, I think
pci_reassign_bridge_resources() needs to do /something/ to ensure that
the resources are reshuffled if needed when the resized BAR overlaps
with another one.

Bjorn, did you have any thoughts on this? I could make
pci_reassign_bridge_resources() take a pci_bus, and handle the root
bus as a special case. Alternatively, pci_resize_resource() could make
the distinction, but it will probably need to duplicate some of the
reassignment that goes on in pci_reassign_bridge_resources() as well.

  reply	other threads:[~2020-04-25 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 16:22 [PATCH] PCI: allow pci_resize_resource() to be used on devices on the root bus Ard Biesheuvel
2020-04-21 16:43 ` Christian König
2020-04-21 17:07   ` Ard Biesheuvel
2020-04-25 17:32     ` Ard Biesheuvel [this message]
2020-04-26  9:08       ` Christian König
2020-04-26  9:58         ` Ard Biesheuvel
2020-04-26 10:46           ` Ard Biesheuvel
2020-04-26 10:53             ` Christian König
2020-04-26 10:59               ` Ard Biesheuvel
2020-04-26 11:27                 ` Christian König
2020-04-26 12:08                   ` Ard Biesheuvel
2020-04-26 12:55                     ` Christian König
2020-04-26 13:04                       ` Ard Biesheuvel
2020-04-26 13:16                         ` Christian König
2020-04-26 10:49           ` Christian König
2020-05-01 17:30 ` 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=CAMj1kXH3WVMehgbMwUEjBSYudAM7PtWAcAYcWspyq4eZJzBwTQ@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=jon@solid-run.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=wasim.khan@nxp.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).