From: Darren Salt <devspam@moreofthesa.me.uk>
To: amd-gfx@lists.freedesktop.org
Cc: Darren Salt <devspam@moreofthesa.me.uk>
Subject: [PATCH 0/7] amdgpu, pci: improved BAR resizing support
Date: Fri, 11 Dec 2020 00:54:59 +0000 [thread overview]
Message-ID: <20201211005506.4554-1-devspam@moreofthesa.me.uk> (raw)
This patch series improves the existing BAR resizing support in amdgpu. By
default, it will attempt to resize BAR0 for each dGPU present to cover the
VRAM, falling back to smaller sizes if necessary, e.g. if there's not enough
address space remaining or support for the size is not advertised.
Basic boot-time (or module load time) options to control this resizing are
implemented: one to control whether resizing is done (and whether the
advertised BAR sizes are ignored) and one to control the maximum BAR size
(where the size would be increased). At present, these are coarse; they
apply to all dGPUs driven by amdgpu.
The override is to cope with GPU VBIOSes which don't properly advertise
supported BAR sizes. This should be quirked somehow; I have yet to determine
how this should be arranged.
Darren Salt (7):
pci: export PCI BAR size-reading functions
pci: add BAR bytes->size helper & expose size->bytes helper
amdgpu: resize BAR0 to the maximum available size, even if it doesn't
cover VRAM (v2)
amdgpu: module option controlling whether BAR0 resizing is done
amdgpu: limit maximum FB BAR size when attempting to enlarge
pci: allow for overriding the list of advertised BAR sizes
amdgpu: allow overriding of the GPU's list of supported BAR sizes
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 +
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 63 ++++++++++++++++++----
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 18 +++++++
drivers/pci/pci.c | 2 +
drivers/pci/pci.h | 6 ---
drivers/pci/setup-res.c | 4 +-
include/linux/pci.h | 15 +++++-
7 files changed, 91 insertions(+), 19 deletions(-)
--
2.20.1
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2020-12-11 0:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 0:54 Darren Salt [this message]
2020-12-11 0:55 ` [PATCH 1/7] pci: export PCI BAR size-reading functions Darren Salt
2020-12-11 9:07 ` Christian König
2020-12-11 0:55 ` [PATCH 2/7] pci: add BAR bytes->size helper & expose size->bytes helper Darren Salt
2020-12-11 0:55 ` [PATCH 3/7] amdgpu: resize BAR0 to the maximum available size, even if it doesn't cover VRAM (v2) Darren Salt
2020-12-11 16:42 ` Christian König
2020-12-11 17:31 ` Darren Salt
2020-12-11 19:06 ` Alex Deucher
2020-12-14 8:12 ` Christian König
2020-12-14 15:46 ` Darren Salt
2020-12-14 20:44 ` Christian König
2020-12-11 0:55 ` [PATCH 4/7] amdgpu: module option controlling whether BAR0 resizing is done Darren Salt
2020-12-11 9:09 ` Christian König
2020-12-11 0:55 ` [PATCH 5/7] amdgpu: limit maximum FB BAR size when attempting to enlarge Darren Salt
2020-12-11 0:55 ` [PATCH 6/7] pci: allow for overriding the list of advertised BAR sizes Darren Salt
2020-12-11 0:55 ` [PATCH 7/7] amdgpu: allow overriding of the GPU's list of supported " Darren Salt
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=20201211005506.4554-1-devspam@moreofthesa.me.uk \
--to=devspam@moreofthesa.me.uk \
--cc=amd-gfx@lists.freedesktop.org \
/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