Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 07/11] drm/xe/xe2hpg: Remove extra allocation of CCS pages for dgfx
Date: Mon, 8 Apr 2024 22:29:34 +0530	[thread overview]
Message-ID: <a6b75448-191a-4f38-b5db-d3c823fde224@intel.com> (raw)
In-Reply-To: <20240408162916.3767771-15-balasubramani.vivekanandan@intel.com>


On 08-04-2024 21:59, Balasubramani Vivekanandan wrote:
> From: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
>
> On Xe2 dGPU, compression is only supported with VRAM. When copying from
> VRAM -> system memory the KMD uses mapping with uncompressed PAT
> so the copy in system memory is guaranteed to be uncompressed.
> When restoring such buffers from system memory -> VRAM the KMD can't
> easily know which pages were originally compressed, so we always use
> uncompressed -> uncompressed here.
> so this means that there's no need for extra CCS storage on such
> platforms.
>
> v2: More description added to commit message
>
> Signed-off-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_bo.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 6166bc715656..fdeb3691d3f6 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -2201,6 +2201,9 @@ bool xe_bo_needs_ccs_pages(struct xe_bo *bo)
>   {
>   	struct xe_device *xe = xe_bo_device(bo);
>   
> +	if (GRAPHICS_VER(xe) >= 20 && IS_DGFX(xe))
> +		return false;
> +

LGTM.

Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

>   	if (!xe_device_has_flat_ccs(xe) || bo->ttm.type != ttm_bo_type_device)
>   		return false;
>   

  reply	other threads:[~2024-04-08 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 16:28 [PATCH v2 00/11] Add Battlemage support Balasubramani Vivekanandan
2024-04-08 16:28 ` [PATCH v2 01/11] drm/xe/xe2: Add workaround 18034896535 Balasubramani Vivekanandan
2024-04-08 16:28 ` [PATCH v2 01/11] drm/xe/xe2: Recognize Xe2_HPG IP Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 02/11] " Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 02/11] drm/xe/xe2: Recognize Xe2_HPM IP Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 03/11] drm/xe/bmg: Add BMG platform definition Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 03/11] drm/xe/xe2: Recognize Xe2_HPM IP Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 04/11] drm/xe/bmg: Add BMG mocs table Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 04/11] drm/xe/bmg: Add BMG platform definition Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 05/11] drm/xe/bmg: Add BMG mocs table Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 05/11] drm/xe/bmg: Program an additional discrete-specific PAT setting Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 06/11] " Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 06/11] drm/xe/xe2hpg: Determine flat ccs offset for vram Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 07/11] " Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 07/11] drm/xe/xe2hpg: Remove extra allocation of CCS pages for dgfx Balasubramani Vivekanandan
2024-04-08 16:59   ` Ghimiray, Himal Prasad [this message]
2024-04-08 16:29 ` [PATCH v2 08/11] drm/xe/xe2: Add workaround 18034896535 Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 08/11] drm/xe/xe2hpg: Remove extra allocation of CCS pages for dgfx Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 09/11] drm/xe/xe2hpg: Add initial GT workarounds Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 10/11] drm/xe/xe2hpg: Introduce performance tuning changes for Xe2_HPG Balasubramani Vivekanandan
2024-04-08 16:29 ` [PATCH v2 11/11] drm/xe/xe2hpm: Add initial set of workarounds Balasubramani Vivekanandan

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=a6b75448-191a-4f38-b5db-d3c823fde224@intel.com \
    --to=himal.prasad.ghimiray@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