Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Oak Zeng <oak.zeng@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Trace xe_bo_validate
Date: Tue, 03 Dec 2024 08:09:39 +0100	[thread overview]
Message-ID: <c3fe010ee6dc51ea75bad670be5296784beb262d.camel@linux.intel.com> (raw)
In-Reply-To: <20241203022140.1919922-1-oak.zeng@intel.com>

On Mon, 2024-12-02 at 21:21 -0500, Oak Zeng wrote:
> Add a tracepoint for xe_bo_validate function. I found this is
> useful during debug issues.
> 
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>

> ---
>  drivers/gpu/drm/xe/xe_bo.c       | 1 +
>  drivers/gpu/drm/xe/xe_trace_bo.h | 5 +++++
>  2 files changed, 6 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index bdac446bf8c06..3448ede2befa6 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -2004,6 +2004,7 @@ int xe_bo_validate(struct xe_bo *bo, struct
> xe_vm *vm, bool allow_res_evict)
>  		ctx.resv = xe_vm_resv(vm);
>  	}
>  
> +	trace_xe_bo_validate(bo);
>  	return ttm_bo_validate(&bo->ttm, &bo->placement, &ctx);
>  }
>  
> diff --git a/drivers/gpu/drm/xe/xe_trace_bo.h
> b/drivers/gpu/drm/xe/xe_trace_bo.h
> index c6d3140542cff..e393a2dd83dbe 100644
> --- a/drivers/gpu/drm/xe/xe_trace_bo.h
> +++ b/drivers/gpu/drm/xe/xe_trace_bo.h
> @@ -53,6 +53,11 @@ DEFINE_EVENT(xe_bo, xe_bo_create,
>  	     TP_ARGS(bo)
>  );
>  
> +DEFINE_EVENT(xe_bo, xe_bo_validate,
> +	     TP_PROTO(struct xe_bo *bo),
> +	     TP_ARGS(bo)
> +);
> +
>  TRACE_EVENT(xe_bo_move,
>  	    TP_PROTO(struct xe_bo *bo, uint32_t new_placement,
> uint32_t old_placement,
>  		     bool move_lacks_source),


  parent reply	other threads:[~2024-12-03  7:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  2:21 [PATCH] drm/xe: Trace xe_bo_validate Oak Zeng
2024-12-03  2:59 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-03  3:00 ` ✓ CI.checkpatch: " Patchwork
2024-12-03  3:01 ` ✓ CI.KUnit: " Patchwork
2024-12-03  3:19 ` ✓ CI.Build: " Patchwork
2024-12-03  3:21 ` ✓ CI.Hooks: " Patchwork
2024-12-03  3:23 ` ✓ CI.checksparse: " Patchwork
2024-12-03  3:44 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-03  4:38 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-03  7:09 ` Thomas Hellström [this message]
2024-12-06 14:40   ` [PATCH] " Rodrigo Vivi

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=c3fe010ee6dc51ea75bad670be5296784beb262d.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=oak.zeng@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