Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jahagirdar, Akshata" <akshata.jahagirdar@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 08/11] drm/xe/xe2hpg: Limit chunk size to 4MiB for vram
Date: Fri, 5 Apr 2024 19:28:09 -0700	[thread overview]
Message-ID: <05fefe56-073b-413b-b8fb-86a8cc53ee8b@intel.com> (raw)
In-Reply-To: <20240404000638.GU6571@mdroper-desk1.amr.corp.intel.com>

This patch was originally sent due to the flat ccs copy  i.e. 
XY_CTRL_SURF_COPY_BLT instruction limitations,
however after working on the implementation of BMG compression,
I have realised that we don't need this patch anymore.
The reason being that we don't need to handle the copying of ccs 
metadata during migration.
For eviction (VRAM -> SMEM) we use compressed -> uncompressed mapping.
But for SMEM -> VRAM we need uncompressed -> uncompressed mapping since 
we don't know
which pages were originally compressed. So, we don't need to handle the 
flat ccs copy here.
We can remove this patch from next series.

--Akshata

On 4/3/2024 5:06 PM, Matt Roper wrote:
> On Tue, Apr 02, 2024 at 06:17:21PM +0530, Balasubramani Vivekanandan wrote:
>> From: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
>>
>> Currently, The maximum chunk size for vram copy is 8 MiB, which means
>> flat ccs copy would be able handle 8 MiB/(page_sizes).  Since page size
>> for vram is 4k the value will be 2048 pages which won't fit in 10
>> bitspace.
>>
>> Therefore we need to limit chunk size to 4MiB the way it is for LNL.
> I found this explanation a bit hard to follow, you might want to clarify
> that it's the XY_CTRL_SURF_COPY_BLT instruction specifically that drives
> this limit.  I.e., the change on Xe2 is that the size provided to that
> instruction now represents one less than the number of 4K pages of the
> main surface for which CCS data needs to be copied.  Since that field is
> 10-bits, we can only copy CCS data that corresponds to 1024 * 4k.
>
> Although now I'm wondering when we actually wind up needing to copy CCS
> data directly on Xe2?  With compression controlled by PAT bits in the
> PTE, doesn't the writing of the FlatCCS metadata happen automatically on
> all main surface copies (both for compressed and non-compressed
> surfaces)?
>
>
> Matt
>
>> Signed-off-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
>> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_migrate.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_migrate.c b/drivers/gpu/drm/xe/xe_migrate.c
>> index ee1bb938c493..07a09649787d 100644
>> --- a/drivers/gpu/drm/xe/xe_migrate.c
>> +++ b/drivers/gpu/drm/xe/xe_migrate.c
>> @@ -407,7 +407,7 @@ struct xe_migrate *xe_migrate_init(struct xe_tile *tile)
>>   
>>   static u64 max_mem_transfer_per_pass(struct xe_device *xe)
>>   {
>> -	if (!IS_DGFX(xe) && xe_device_has_flat_ccs(xe))
>> +	if (GRAPHICS_VER(xe) >= 20 && xe_device_has_flat_ccs(xe))
>>   		return MAX_CCS_LIMITED_TRANSFER;
>>   
>>   	return MAX_PREEMPTDISABLE_TRANSFER;
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2024-04-06  2:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 12:47 [PATCH 00/11] Add Battlemage support Balasubramani Vivekanandan
2024-04-02 12:47 ` [PATCH 01/11] drm/xe/xe2: Recognize Xe2_HPG IP Balasubramani Vivekanandan
2024-04-02 13:21   ` Lucas De Marchi
2024-04-02 12:47 ` [PATCH 02/11] drm/xe/xe2: Recognize Xe2_HPM IP Balasubramani Vivekanandan
2024-04-02 13:22   ` Lucas De Marchi
2024-04-02 12:47 ` [PATCH 03/11] drm/xe/bmg: Add BMG platform definition Balasubramani Vivekanandan
2024-04-02 13:26   ` Lucas De Marchi
2024-04-02 12:47 ` [PATCH 04/11] drm/xe/bmg: Add BMG mocs table Balasubramani Vivekanandan
2024-04-02 13:52   ` Matt Roper
2024-04-02 12:47 ` [PATCH 05/11] drm/xe/bmg: Program an additional discrete-specific PAT setting Balasubramani Vivekanandan
2024-04-02 12:47 ` [PATCH 06/11] drm/xe/xe2hpg: Determine flat ccs offset for vram Balasubramani Vivekanandan
2024-04-02 14:30   ` Matt Roper
2024-04-03  6:53     ` Vivekanandan, Balasubramani
2024-04-05  9:48       ` Vivekanandan, Balasubramani
2024-04-02 12:47 ` [PATCH 07/11] drm/xe/xe2hpg: Remove extra allocation of CCS pages for dgfx Balasubramani Vivekanandan
2024-04-02 14:40   ` Matt Roper
2024-04-02 12:47 ` [PATCH 08/11] drm/xe/xe2hpg: Limit chunk size to 4MiB for vram Balasubramani Vivekanandan
2024-04-04  0:06   ` Matt Roper
2024-04-06  2:28     ` Jahagirdar, Akshata [this message]
2024-04-02 12:47 ` [PATCH 09/11] drm/xe/xe2hpg: Add initial GT workarounds Balasubramani Vivekanandan
2024-04-02 15:45   ` Matt Roper
2024-04-02 19:14     ` Matt Roper
2024-04-02 12:47 ` [PATCH 10/11] drm/xe/xe2hpg: Introduce performance tuning changes for Xe2_HPG Balasubramani Vivekanandan
2024-04-02 15:55   ` Matt Roper
2024-04-02 12:47 ` [PATCH 11/11] drm/xe/xe2hpm: Add initial set of workarounds Balasubramani Vivekanandan
2024-04-02 16:07   ` Matt Roper
2024-04-02 12:53 ` ✓ CI.Patch_applied: success for Add Battlemage support Patchwork
2024-04-02 12:53 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-02 12:54 ` ✓ CI.KUnit: success " Patchwork
2024-04-02 13:05 ` ✓ CI.Build: " Patchwork
2024-04-02 13:08 ` ✓ CI.Hooks: " Patchwork
2024-04-02 13:09 ` ✓ CI.checksparse: " Patchwork
2024-04-02 13:46 ` ✓ CI.BAT: " 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=05fefe56-073b-413b-b8fb-86a8cc53ee8b@intel.com \
    --to=akshata.jahagirdar@intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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