From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Akshata Jahagirdar <akshata.jahagirdar@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <akshatajahagirdar6@gmail.com>
Subject: Re: [PATCH 0/6] Implement compression support on BMG
Date: Thu, 11 Jul 2024 18:04:21 +0530 [thread overview]
Message-ID: <1d59d288-b8f3-4125-b837-2ca3e479bf29@intel.com> (raw)
In-Reply-To: <cover.1720515376.git.akshata.jahagirdar@intel.com>
On 11-07-2024 11:24, Akshata Jahagirdar wrote:
> On Xe2 the compression has moved to a unified universal model
> (exactly one compression mode/format), where compression is now
> controlled via PAT on per-page basis. This now means KMD can
> decompress freely. This was problematic on DG2 since we had
> multiple compression formats, and the compression format used
> on a particular buffer was unknown to the KMD, so instead the
> raw CCS state needed to be copied around when evicting VRAM.
> In addition mixed VRAM and system memory buffers were not
> supported with compression enabled.
>
> On Xe2 dGPU compression is still only supported with VRAM,
> however we can now support compression with VRAM and system
> memory buffers, with GPU access being seamless underneath.
> So long as when doing VRAM -> sysmem the KMD does the move
> using compressed -> uncompressed, to decompress it.
> CPU access to such buffers is also possible, under the premise
> that userspace first decompress the corresponding pages being
> accessed. If the pages are already in system memory then KMD would
> have already decompressed them. When restoring such buffers with
> sysmem -> VRAM the KMD can't easily know which pages were originally
> compressed, so we always use uncompressed -> uncompressed here.
> With this it also means we can drop all the raw CCS handling
> on such platforms (including needing to allocate extra CCS storage).
>
> In order to support this we now need to have two different identity
> mappings for compressed and uncompressed VRAM.
> The additional identity map is the VRAM with compressed pat_index.
> We then select the appropriate mapping during migration/clear.
>
Have gone through all the patches. Please address indentation and
checkpatch errors.
With above addressed all patches lgtm.
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Akshata Jahagirdar (6):
> drm/xe/xe2: Introduce identity map for compressed pat for vram
> drm/xe/migrate: Handle clear ccs logic for xe2 dgfx
> drm/xe/migrate: Add kunit to test clear functionality
> drm/xe/xe_migrate: Handle migration logic for xe2+ dgfx
> drm/xe/migrate: Add kunit to test migration functionality for BMG
> drm/xe/xe2: Do not run xe_bo_test for xe2+ dgfx
>
> drivers/gpu/drm/xe/tests/xe_bo.c | 6 +
> drivers/gpu/drm/xe/tests/xe_migrate.c | 388 +++++++++++++++++++++
> drivers/gpu/drm/xe/tests/xe_migrate_test.c | 1 +
> drivers/gpu/drm/xe/tests/xe_migrate_test.h | 1 +
> drivers/gpu/drm/xe/xe_device.h | 5 +
> drivers/gpu/drm/xe/xe_migrate.c | 66 +++-
> 6 files changed, 449 insertions(+), 18 deletions(-)
>
next prev parent reply other threads:[~2024-07-11 12:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 7:53 [PATCH 0/6] Implement compression support on BMG Akshata Jahagirdar
2024-07-09 10:33 ` Matthew Auld
2024-07-09 19:07 ` Jahagirdar, Akshata
2024-07-10 7:53 ` [PATCH 1/6] drm/xe/migrate: Handle clear ccs logic for xe2 dgfx Akshata Jahagirdar
2024-07-10 8:01 ` Nirmoy Das
2024-07-10 8:17 ` Akshata Jahagirdar
2024-07-11 11:27 ` Akshata Jahagirdar
2024-07-11 12:42 ` Akshata Jahagirdar
2024-07-11 13:07 ` Akshata Jahagirdar
2024-07-12 11:52 ` [PATCH 1/6] drm/xe/migrate: Sample patch for testing Akshata Jahagirdar
2024-07-12 11:53 ` Akshata Jahagirdar
2024-07-10 8:17 ` [PATCH 0/6] Implement compression support on BMG Akshata Jahagirdar
2024-07-11 5:54 ` Akshata Jahagirdar
2024-07-11 11:27 ` Akshata Jahagirdar
2024-07-11 12:34 ` Ghimiray, Himal Prasad [this message]
2024-07-11 12:42 ` Akshata Jahagirdar
2024-07-11 13:07 ` Akshata Jahagirdar
-- strict thread matches above, loose matches on Subject: below --
2024-07-11 9:18 Akshata Jahagirdar
2024-07-11 9:19 ` Akshata Jahagirdar
2024-07-12 6:39 Akshata Jahagirdar
2024-07-12 7:24 ` Akshata Jahagirdar
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=1d59d288-b8f3-4125-b837-2ca3e479bf29@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=akshata.jahagirdar@intel.com \
--cc=akshatajahagirdar6@gmail.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