From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [PATCH 0/2] Set 64k physical alignment on display buffers for CCS.
Date: Wed, 21 Aug 2024 17:05:17 +0200 [thread overview]
Message-ID: <20240821150519.478168-1-maarten.lankhorst@linux.intel.com> (raw)
Instead of restricting display to 64k, keeping allowing any BO size.
Iff a buffer is created with a scanout flag, as a multiple of 64K, it can
be used for CCS.
This should fix the corruption issue, the changes to UMD will be only
setting a multiple of 64K for CCS fb's.
Untested, lets see if it gets through CI. :)
Maarten Lankhorst (1):
drm/xe: Align 64k scanout buffers physically when required
Zbigniew Kempczyński (1):
drm/xe: Use 64K pages for scanout buffers for Battlemage
drivers/gpu/drm/xe/display/intel_fb_bo.c | 6 ++++++
drivers/gpu/drm/xe/xe_bo.c | 17 ++++++++++++++++-
drivers/gpu/drm/xe/xe_device_types.h | 1 +
drivers/gpu/drm/xe/xe_pci.c | 9 ++++++++-
drivers/gpu/drm/xe/xe_vm.c | 4 +++-
5 files changed, 34 insertions(+), 3 deletions(-)
--
2.45.2
next reply other threads:[~2024-08-21 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 15:05 Maarten Lankhorst [this message]
2024-08-21 15:05 ` [PATCH 1/2] drm/xe: Align 64k scanout buffers physically when required Maarten Lankhorst
2024-08-21 15:05 ` [PATCH 2/2] drm/xe: Use 64K pages for scanout buffers for Battlemage Maarten Lankhorst
2024-08-21 15:11 ` ✓ CI.Patch_applied: success for Set 64k physical alignment on display buffers for CCS Patchwork
2024-08-21 15:11 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-21 15:12 ` ✓ CI.KUnit: success " Patchwork
2024-08-21 15:24 ` ✓ CI.Build: " Patchwork
2024-08-21 15:26 ` ✓ CI.Hooks: " Patchwork
2024-08-21 15:27 ` ✓ CI.checksparse: " Patchwork
2024-08-21 15:50 ` ✗ CI.BAT: failure " Patchwork
2024-08-21 17:33 ` ✗ CI.FULL: " 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=20240821150519.478168-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--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