From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [PATCH v3 0/4] drm/xe: More fb pinning optimizations.
Date: Wed, 24 Apr 2024 15:02:58 +0200 [thread overview]
Message-ID: <20240424130302.1603331-1-maarten.lankhorst@linux.intel.com> (raw)
This reduces the latency of pinning framebuffers by
re-using the previous mapping, if available.
Additionally, DPT is preallocated when creating the FB, instead
of performing a bo allocation on every pin.
Remove the safety check in the first patch again, I didn't realize it was
needed even without the initial FB GGTT pinning removal.
Maarten Lankhorst (4):
drm/xe: Remove safety check from __xe_ttm_stolen_io_mem_reserve_stolen
drm/xe/display: Preparations for preallocating dpt bo
drm/xe: Use simple xchg to cache DPT
drm/xe/display: Re-use display vmas when possible
.../gpu/drm/i915/display/intel_atomic_plane.c | 2 +-
drivers/gpu/drm/i915/display/intel_cursor.c | 2 +-
drivers/gpu/drm/i915/display/intel_fb_pin.c | 3 +-
drivers/gpu/drm/i915/display/intel_fb_pin.h | 3 +-
drivers/gpu/drm/i915/display/intel_fbdev.c | 5 +
drivers/gpu/drm/i915/display/intel_fbdev.h | 9 +
.../gpu/drm/xe/compat-i915-headers/i915_vma.h | 3 +
drivers/gpu/drm/xe/display/xe_fb_pin.c | 220 ++++++++++++++----
drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c | 4 -
9 files changed, 198 insertions(+), 53 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-24 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 13:02 Maarten Lankhorst [this message]
2024-04-24 13:02 ` [PATCH v3 1/4] drm/xe: Remove safety check from __xe_ttm_stolen_io_mem_reserve_stolen Maarten Lankhorst
2024-04-24 13:03 ` [PATCH v3 2/4] drm/xe/display: Preparations for preallocating dpt bo Maarten Lankhorst
2024-04-24 13:03 ` [PATCH v3 3/4] drm/xe: Use simple xchg to cache DPT Maarten Lankhorst
2024-04-24 13:03 ` [PATCH v3 4/4] drm/xe/display: Re-use display vmas when possible Maarten Lankhorst
2024-04-24 14:50 ` ✗ Fi.CI.CHECKPATCH: warning for drm/xe: More fb pinning optimizations Patchwork
2024-04-24 14:58 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-24 20:35 ` ✗ Fi.CI.IGT: failure " Patchwork
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=20240424130302.1603331-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).