Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, umesh.nerlige.ramappa@intel.com,
	riana.tauro@intel.com
Subject: Re: [PATCH 2/3] drm/xe: Restore system memory GGTT mappings
Date: Tue, 29 Oct 2024 09:44:32 +0000	[thread overview]
Message-ID: <326aaf08-60ef-4eb8-8565-093488b4c9d3@intel.com> (raw)
In-Reply-To: <20241029003224.2257439-3-matthew.brost@intel.com>

On 29/10/2024 00:32, Matthew Brost wrote:
> GGTT mappings reside on the device and this state is lost during suspend
> / d3cold thus this state must be restored resume regardless if the BO is
> in system memory or VRAM.
> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

I think this needs fixes?

> ---
>   drivers/gpu/drm/xe/xe_bo.c       | 14 +++++++++++---
>   drivers/gpu/drm/xe/xe_bo_evict.c |  1 -
>   2 files changed, 11 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index bd747e53eb9b..6c8fd5ced2a2 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -890,8 +890,8 @@ int xe_bo_evict_pinned(struct xe_bo *bo)
>   	if (WARN_ON(!xe_bo_is_pinned(bo)))
>   		return -EINVAL;
>   
> -	if (WARN_ON(!xe_bo_is_vram(bo)))
> -		return -EINVAL;
> +	if (!xe_bo_is_vram(bo))
> +		return 0;

In the suspend flow in xe_bo_evict_all() there is:

	if (!IS_DGFX(xe))
		return 0;

But seems like we now need this flow for igpu, so need to also drop that 
check?

>   
>   	if (bo->flags & XE_BO_FLAG_PINNED_WONTNEED) {
>   		ttm_bo_move_null(&bo->ttm, NULL);
> @@ -946,6 +946,7 @@ int xe_bo_restore_pinned(struct xe_bo *bo)
>   		.interruptible = false,
>   	};
>   	struct ttm_resource *new_mem;
> +	struct ttm_place *place = &(bo->placements[0]);
>   	int ret;
>   
>   	xe_bo_assert_held(bo);
> @@ -961,6 +962,9 @@ int xe_bo_restore_pinned(struct xe_bo *bo)
>   			return -EINVAL;
>   	}
>   
> +	if (!mem_type_is_vram(place->mem_type))
> +		return 0;
> +
>   	ret = ttm_bo_mem_space(&bo->ttm, &bo->placement, &new_mem, &ctx);
>   	if (ret)
>   		return ret;
> @@ -1814,7 +1818,10 @@ int xe_bo_pin(struct xe_bo *bo)
>   			place->fpfn = (xe_bo_addr(bo, 0, PAGE_SIZE) -
>   				       vram_region_gpu_offset(bo->ttm.resource)) >> PAGE_SHIFT;
>   			place->lpfn = place->fpfn + (bo->size >> PAGE_SHIFT);
> +		}
>   
> +		if (mem_type_is_vram(place->mem_type) ||
> +		    bo->flags & XE_BO_FLAG_GGTT) {
>   			spin_lock(&xe->pinned.lock);
>   			list_add_tail(&bo->pinned_link, &xe->pinned.kernel_bo_present);
>   			spin_unlock(&xe->pinned.lock);
> @@ -1875,7 +1882,8 @@ void xe_bo_unpin(struct xe_bo *bo)
>   	    bo->flags & XE_BO_FLAG_INTERNAL_TEST)) {
>   		struct ttm_place *place = &(bo->placements[0]);
>   
> -		if (mem_type_is_vram(place->mem_type)) {
> +		if (mem_type_is_vram(place->mem_type) ||
> +		    bo->flags & XE_BO_FLAG_GGTT) {
>   			spin_lock(&xe->pinned.lock);
>   			xe_assert(xe, !list_empty(&bo->pinned_link));
>   			list_del_init(&bo->pinned_link);
> diff --git a/drivers/gpu/drm/xe/xe_bo_evict.c b/drivers/gpu/drm/xe/xe_bo_evict.c
> index 541b49007d73..32043e1e5a86 100644
> --- a/drivers/gpu/drm/xe/xe_bo_evict.c
> +++ b/drivers/gpu/drm/xe/xe_bo_evict.c
> @@ -159,7 +159,6 @@ int xe_bo_restore_kernel(struct xe_device *xe)
>   		 * should setup the iosys map.
>   		 */
>   		xe_assert(xe, !iosys_map_is_null(&bo->vmap));
> -		xe_assert(xe, xe_bo_is_vram(bo));
>   
>   		xe_bo_put(bo);
>   

  reply	other threads:[~2024-10-29  9:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  0:32 [PATCH 0/3] Suspend, resume, and d3cold tweaks Matthew Brost
2024-10-29  0:32 ` [PATCH 1/3] drm/xe: Add XE_BO_FLAG_PINNED_WONTNEED Matthew Brost
2024-10-29 13:30   ` Rodrigo Vivi
2024-10-29 14:55     ` Matthew Brost
2024-10-31  4:23       ` Lucas De Marchi
2024-10-31  5:10         ` Matthew Brost
2024-10-29  0:32 ` [PATCH 2/3] drm/xe: Restore system memory GGTT mappings Matthew Brost
2024-10-29  9:44   ` Matthew Auld [this message]
2024-10-29 14:57     ` Matthew Brost
2024-10-30 11:53       ` Matthew Auld
2024-10-31  0:49         ` Matthew Brost
2024-10-31  8:44   ` Matthew Auld
2024-10-29  0:32 ` [PATCH 3/3] drm/xe: Add XE_BO_FLAG_PINNED_NEED_LOAD Matthew Brost
2024-10-29  1:07   ` Matthew Brost
2024-10-29  0:44 ` ✓ CI.Patch_applied: success for Suspend, resume, and d3cold tweaks Patchwork
2024-10-29  0:45 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-29  0:46 ` ✓ CI.KUnit: success " Patchwork
2024-10-29  0:58 ` ✓ CI.Build: " Patchwork
2024-10-29  1:00 ` ✓ CI.Hooks: " Patchwork
2024-10-29  1:01 ` ✓ CI.checksparse: " Patchwork
2024-10-29  1:29 ` ✗ 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=326aaf08-60ef-4eb8-8565-093488b4c9d3@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=umesh.nerlige.ramappa@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