Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Add debug prints for skipping rebinds
Date: Wed, 21 Feb 2024 16:13:31 -0500	[thread overview]
Message-ID: <ZdZne68d1T0_v8Sz@intel.com> (raw)
In-Reply-To: <20240221032743.3698849-1-matthew.brost@intel.com>

On Tue, Feb 20, 2024 at 07:27:43PM -0800, Matthew Brost wrote:
> Will help debug issues with VM binds.

worth adding more cases?

anyway,

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_vm.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 23a44ef85aa4..bf040df0d02b 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -2287,6 +2287,7 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm, struct xe_exec_queue *q,
>  				   struct xe_sync_entry *syncs, u32 num_syncs,
>  				   struct list_head *ops_list, bool last)
>  {
> +	struct xe_device *xe = vm->xe;
>  	struct xe_vma_op *last_op = NULL;
>  	struct drm_gpuva_op *__op;
>  	int err = 0;
> @@ -2362,6 +2363,9 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm, struct xe_exec_queue *q,
>  						xe_vma_end(vma) -
>  						xe_vma_start(old);
>  					op->remap.start = xe_vma_end(vma);
> +					vm_dbg(&xe->drm, "REMAP:SKIP_PREV: addr=0x%016llx, range=0x%016llx",
> +					       (ULL)op->remap.start,
> +					       (ULL)op->remap.range);
>  				}
>  			}
>  
> @@ -2392,6 +2396,9 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm, struct xe_exec_queue *q,
>  					op->remap.range -=
>  						xe_vma_end(old) -
>  						xe_vma_start(vma);
> +					vm_dbg(&xe->drm, "REMAP:SKIP_NEXT: addr=0x%016llx, range=0x%016llx",
> +					       (ULL)op->remap.start,
> +					       (ULL)op->remap.range);
>  				}
>  			}
>  			break;
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2024-02-21 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  3:27 [PATCH] drm/xe: Add debug prints for skipping rebinds Matthew Brost
2024-02-21  3:31 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-21  3:31 ` ✓ CI.checkpatch: " Patchwork
2024-02-21  3:32 ` ✓ CI.KUnit: " Patchwork
2024-02-21  3:43 ` ✓ CI.Build: " Patchwork
2024-02-21  3:44 ` ✓ CI.Hooks: " Patchwork
2024-02-21  3:45 ` ✓ CI.checksparse: " Patchwork
2024-02-21  4:06 ` ✓ CI.BAT: " Patchwork
2024-02-21 21:13 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-22  3:47 [PATCH 0/2] Fix execlist mode Matthew Brost
2024-02-22  3:47 ` [PATCH] drm/xe: Add debug prints for skipping rebinds Matthew Brost

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=ZdZne68d1T0_v8Sz@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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