From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Hellstrom Thomas <thomas.hellstrom@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: [Intel-gfx] [PATCH v5 0/9] drm/i915/ttm: Evict and restore of compressed object
Date: Tue, 22 Mar 2022 04:14:50 +0530 [thread overview]
Message-ID: <20220321224459.12223-1-ramalingam.c@intel.com> (raw)
On Xe-HP and later devices, we use dedicated compression control
state (CCS) stored in local memory for each surface, to support
the 3D and media compression formats.
The memory required for the CCS of the entire local memory is
1/256 of the local memory size. So before the kernel
boot, the required memory is reserved for the CCS data and a
secure register will be programmed with the CCS base address
So when we allocate a object in local memory we dont need to explicitly
allocate the space for ccs data. But when we evict the obj into the smem
to hold the compression related data along with the obj we need smem
space of obj_size + (obj_size/256).
Hence when we create smem for an obj with lmem placement possibility we
create with the extra space.
When we are swapping out the local memory obj on flat-ccs capable platform,
we need to capture the ccs data too along with main meory and we need to
restore it when we are swapping in the content.
When lmem object is swapped into a smem obj, smem obj will
have the extra pages required to hold the ccs data corresponding to the
lmem main memory. So main memory of lmem will be copied into the initial
pages of the smem and then ccs data corresponding to the main memory
will be copied to the subsequent pages of smem.
Swapin happens exactly in reverse order. First main memory of lmem is
restored from the smem's initial pages and the ccs data will be restored
from the subsequent pages of smem.
Extracting and restoring the CCS data is done through a special cmd called
XY_CTRL_SURF_COPY_BLT
v5:
Correct locating of ccs data [Thomas]
Reuse of emit_copy_ccs.
R-bs picked.
Test-with: 20220314051432.15785-1-ramalingam.c@intel.com
Ramalingam C (9):
drm/i915/gt: Use XY_FAST_COLOR_BLT to clear obj on graphics ver 12+
drm/i915/gt: Optimize the migration and clear loop
drm/i915/gt: Clear compress metadata for Flat-ccs objects
drm/i915/selftest_migrate: Consider the possible roundup of size
drm/i915/selftest_migrate: Check CCS meta data clear
drm/i915/gt: offset handling for multiple copy engines
drm/ttm: Add a parameter to add extra pages into ttm_tt
drm/i915/gem: Add extra pages in ttm_tt for ccs data
drm/i915/migrate: Evict and restore the flatccs capable lmem obj
drivers/gpu/drm/drm_gem_vram_helper.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 29 +-
drivers/gpu/drm/i915/gt/intel_gpu_commands.h | 20 +
drivers/gpu/drm/i915/gt/intel_migrate.c | 409 +++++++++++++++++--
drivers/gpu/drm/i915/gt/selftest_migrate.c | 253 ++++++++++--
drivers/gpu/drm/qxl/qxl_ttm.c | 2 +-
drivers/gpu/drm/ttm/ttm_agp_backend.c | 2 +-
drivers/gpu/drm/ttm/ttm_tt.c | 12 +-
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c | 2 +-
include/drm/ttm/ttm_tt.h | 4 +-
10 files changed, 664 insertions(+), 71 deletions(-)
--
2.20.1
next reply other threads:[~2022-03-21 22:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 22:44 Ramalingam C [this message]
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 1/9] drm/i915/gt: Use XY_FAST_COLOR_BLT to clear obj on graphics ver 12+ Ramalingam C
2022-03-22 10:10 ` Thomas Hellström
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 2/9] drm/i915/gt: Optimize the migration and clear loop Ramalingam C
2022-03-24 15:35 ` Thomas Hellström (Intel)
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 3/9] drm/i915/gt: Clear compress metadata for Flat-ccs objects Ramalingam C
2022-03-24 16:14 ` Thomas Hellström (Intel)
2022-03-28 18:59 ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 4/9] drm/i915/selftest_migrate: Consider the possible roundup of size Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 5/9] drm/i915/selftest_migrate: Check CCS meta data clear Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 6/9] drm/i915/gt: offset handling for multiple copy engines Ramalingam C
2022-03-24 16:20 ` Thomas Hellström (Intel)
2022-03-28 18:56 ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 7/9] drm/ttm: Add a parameter to add extra pages into ttm_tt Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 8/9] drm/i915/gem: Add extra pages in ttm_tt for ccs data Ramalingam C
2022-03-24 16:28 ` Thomas Hellström
2022-03-28 18:57 ` Ramalingam C
2022-03-21 22:44 ` [Intel-gfx] [PATCH v5 9/9] drm/i915/migrate: Evict and restore the flatccs capable lmem obj Ramalingam C
2022-03-22 11:20 ` [Intel-gfx] [PATCH v6 " Ramalingam C
2022-03-22 1:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: Evict and restore of compressed object (rev3) Patchwork
2022-03-22 1:49 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22 1:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 2:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-22 12:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: Evict and restore of compressed object (rev4) Patchwork
2022-03-22 12:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-22 12:08 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 12:34 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20220321224459.12223-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@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