From: Matthew Auld <matthew.auld@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, dri-devel@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
"Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Akshata Jahagirdar" <akshata.jahagirdar@intel.com>
Subject: Re: [PATCH v6 2/3] drm/xe/migrate: Parameterize ccs and bo data clear in xe_migrate_clear()
Date: Fri, 9 Aug 2024 11:46:02 +0100 [thread overview]
Message-ID: <b8a2a796-719d-48db-b474-a39feb50975e@intel.com> (raw)
In-Reply-To: <20240719095506.4068-2-nirmoy.das@intel.com>
On 19/07/2024 10:55, Nirmoy Das wrote:
> Parameterize clearing ccs and bo data in xe_migrate_clear() which higher
> layers can utilize. This patch will be used later on when doing bo data
> clear for igfx as well.
>
> v2: Replace multiple params with flags in xe_migrate_clear (Matt B)
> v3: s/CLEAR_BO_DATA_FLAG_*/XE_MIGRATE_CLEAR_FLAG_* and move to
> xe_migrate.h. other nits(Matt B)
>
> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> Signed-off-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
Seems reasonable to me,
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2024-08-09 10:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 9:55 [PATCH v6 1/3] drm/ttm: Add a flag to allow drivers to skip clear-on-free Nirmoy Das
2024-07-19 9:55 ` [PATCH v6 2/3] drm/xe/migrate: Parameterize ccs and bo data clear in xe_migrate_clear() Nirmoy Das
2024-08-09 10:46 ` Matthew Auld [this message]
2024-07-19 9:55 ` [PATCH v6 3/3] drm/xe/lnl: Offload system clear page activity to GPU Nirmoy Das
2024-07-22 7:50 ` Matthew Brost
2024-07-22 8:35 ` Nirmoy Das
2024-07-19 10:17 ` ✓ CI.Patch_applied: success for series starting with [v6,1/3] drm/ttm: Add a flag to allow drivers to skip clear-on-free Patchwork
2024-07-19 10:17 ` ✓ CI.checkpatch: " Patchwork
2024-07-19 10:18 ` ✗ CI.KUnit: failure " Patchwork
2024-07-22 5:00 ` ✓ CI.Patch_applied: success for series starting with [v6,1/3] drm/ttm: Add a flag to allow drivers to skip clear-on-free (rev2) Patchwork
2024-07-22 5:01 ` ✓ CI.checkpatch: " Patchwork
2024-07-22 5:02 ` ✓ CI.KUnit: " Patchwork
2024-07-22 5:14 ` ✓ CI.Build: " Patchwork
2024-07-22 5:16 ` ✓ CI.Hooks: " Patchwork
2024-07-22 5:18 ` ✗ CI.checksparse: warning " Patchwork
2024-07-22 5:37 ` ✓ CI.BAT: success " Patchwork
2024-07-22 7:57 ` ✗ CI.FULL: 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=b8a2a796-719d-48db-b474-a39feb50975e@intel.com \
--to=matthew.auld@intel.com \
--cc=akshata.jahagirdar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@intel.com \
--cc=thomas.hellstrom@linux.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