From: Alex Williamson <alex.williamson@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: PCI resource allocation mismatch with BIOS
Date: Mon, 28 Nov 2022 15:06:17 -0700 [thread overview]
Message-ID: <20221128150617.14c98c2e.alex.williamson@redhat.com> (raw)
In-Reply-To: <20221128203932.GA644781@bhelgaas>
On Mon, 28 Nov 2022 14:39:32 -0600
Bjorn Helgaas <helgaas@kernel.org> wrote:
> [+cc Alex]
>
> Hi Mika,
>
> On Mon, Nov 28, 2022 at 01:14:14PM +0200, Mika Westerberg wrote:
> > Hi Bjorn,
> >
> > There is another PCI resource allocation issue with some Intel GPUs but
> > probably applies to other similar devices as well. This is something
> > encountered in data centers where they trigger reset (secondary bus
> > reset) to the GPUs if there is hang or similar detected. Basically they
> > do something like:
> >
> > 1. Unbind the graphics driver(s) through sysfs.
> > 2. Remove the PCIe devices under the root port or the PCIe switch
> > upstream port through sysfs (echo 1 > ../remove).
> > 3. Trigger reset through config space or use the sysfs reset attribute.
> > 4. Run rescan on the root bus (echo 1 > /sys/bus/pci/rescan)
> >
> > Expectation is to see the devices come back in the same way prior the
> > reset but what actually happens is that the Linux PCI resource
> > allocation fails to allocate space for some of the resources. In this
> > case it is the IOV BARs.
> >
> > BIOS allocates resources for all these at boot time but after the rescan
> > Linux tries to re-allocate them but since the allocation algorithm is
> > more "consuming" some of the BARs do not fit to the available resource
> > space.
>
> Thanks for the report! Definitely sounds like an issue. I doubt that
> I'll have time to work on it myself in the near future.
>
> Is the "remove" before the reset actually necessary? If we could
> avoid the removal, maybe the config space save/restore we already do
> around reset would avoid the issue?
Agreed. Is this convoluted removal process being used to force a SBR,
versus a FLR or PM reset that might otherwise be used by twiddling the
reset attribute of the GPU directly? If so, the reset_method attribute
can be used to force a bus reset and perform all the state save/restore
handling to avoid reallocating BARs. A reset from the upstream switch
port would only be necessary if you have some reason to also reset the
switch downstream ports. Thanks,
Alex
next prev parent reply other threads:[~2022-11-28 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:14 PCI resource allocation mismatch with BIOS Mika Westerberg
2022-11-28 20:39 ` Bjorn Helgaas
2022-11-28 22:06 ` Alex Williamson [this message]
2022-11-29 6:48 ` Lukas Wunner
2022-11-29 10:09 ` Mika Westerberg
2022-11-29 13:52 ` Alex Williamson
2022-11-29 15:07 ` Mika Westerberg
2022-11-29 15:46 ` Alex Williamson
2022-11-29 16:06 ` Lukas Wunner
2022-11-29 16:12 ` Alex Williamson
2022-11-30 7:43 ` Lukas Wunner
2022-11-30 7:57 ` Mika Westerberg
2022-11-30 15:47 ` Alex Williamson
2022-12-01 9:41 ` Mika Westerberg
2022-12-09 11:08 ` 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=20221128150617.14c98c2e.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.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