From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH 0/3] PCI: remove redundant resource assignments done after BAR resize
Date: Mon, 9 Nov 2026 15:10:07 +0200 [thread overview]
Message-ID: <20261109131011.1815-1-ilpo.jarvinen@linux.intel.com> (raw)
The BAR resize rework removed the resource assignment call that
followed the BAR resize in amdgpu. The xe and i915 drivers and the
PCI sysfs resize interface still make the same call.
The current BAR resize code should properly assign all resources and
handle fallback gracefully so a driver-side call to assign resource
right after BAR resize is just duplicate work (no-op). If that isn't
the case somewhere, the fix belongs either the BAR resize code or the
code that left the resource unassigned (e.g. a hotplug race or whatever
left an resource unassigned prior to resize).
If drm wants to take their patches out of these, it's fine with me
(either drm+pci or through pci tree only works for me).
Ilpo Järvinen (3):
PCI/sysfs: Remove resource assignment after BAR resize
drm/xe: Remove driver side resource assignment after BAR resize
drm/i915: Remove driver side resource assignment after BAR resize
drivers/gpu/drm/i915/gt/intel_region_lmem.c | 1 -
drivers/gpu/drm/xe/xe_pci_rebar.c | 2 --
drivers/pci/pci-sysfs.c | 3 ---
3 files changed, 6 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.47.3
next reply other threads:[~2026-11-09 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:10 Ilpo Järvinen [this message]
2026-11-09 13:10 ` [PATCH 1/3] PCI/sysfs: Remove resource assignment " Ilpo Järvinen
2026-11-09 13:10 ` [PATCH 2/3] drm/xe: Remove driver side " Ilpo Järvinen
2026-11-09 13:10 ` [PATCH 3/3] drm/i915: " 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=20261109131011.1815-1-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@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
all inboxes | Powered by JetHome®