All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Oak Zeng <oak.zeng@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <Thomas.Hellstrom@linux.intel.com>, <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/3] drm/xe: trace bo create
Date: Mon, 23 Dec 2024 15:54:05 +0530	[thread overview]
Message-ID: <12fb5585-93d5-4e9b-bfdc-36c5c252efca@intel.com> (raw)
In-Reply-To: <20241218164833.2364049-2-oak.zeng@intel.com>



On 18-12-2024 22:18, Oak Zeng wrote:
> Add a tracepoint to trace bo create.
> 
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
> Reviewed-by: Matthew Brost <matthew.brost@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 abdeed1c325ea..61f4326e96504 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -1649,6 +1649,7 @@ __xe_bo_create_locked(struct xe_device *xe,
>   		}
>   	}
>   
> +	trace_xe_bo_create(bo);
>   	return bo;
>   
>   err_unlock_put_bo:
> diff --git a/drivers/gpu/drm/xe/xe_trace_bo.h b/drivers/gpu/drm/xe/xe_trace_bo.h
> index 1762dd30ba6dc..53807f2ef4808 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_validate,
>   	     TP_ARGS(bo)
>   );
>   
> +DEFINE_EVENT(xe_bo, xe_bo_create,
> +	     TP_PROTO(struct xe_bo *bo),
> +	     TP_ARGS(bo)
> +);
> +

Looks good.
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

>   TRACE_EVENT(xe_bo_move,
>   	    TP_PROTO(struct xe_bo *bo, uint32_t new_placement, uint32_t old_placement,
>   		     bool move_lacks_source),


  reply	other threads:[~2024-12-23 10:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 16:48 [PATCH 0/3] drm/xe: Small trace print improvements Oak Zeng
2024-12-18 16:48 ` [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-12-23 10:24   ` Ghimiray, Himal Prasad [this message]
2024-12-18 16:48 ` [PATCH 2/3] drm/xe: Print vm flags in xe_vm trace print Oak Zeng
2024-12-23 10:25   ` Ghimiray, Himal Prasad
2024-12-18 16:48 ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Oak Zeng
2024-12-23 10:26   ` Ghimiray, Himal Prasad
2024-12-18 23:34 ` ✓ CI.Patch_applied: success for drm/xe: Small trace print improvements (rev2) Patchwork
2024-12-18 23:34 ` ✓ CI.checkpatch: " Patchwork
2024-12-18 23:35 ` ✓ CI.KUnit: " Patchwork
2024-12-18 23:53 ` ✓ CI.Build: " Patchwork
2024-12-18 23:55 ` ✓ CI.Hooks: " Patchwork
2024-12-18 23:57 ` ✓ CI.checksparse: " Patchwork
2024-12-19  0:30 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-19 16:59 ` ✗ Xe.CI.Full: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-12-17 23:14 [PATCH 0/3] drm/xe: Small trace print improvements Oak Zeng
2024-12-17 23:14 ` [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-12-18  3:05   ` Matthew Brost
2024-11-28 22:09 Oak Zeng

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=12fb5585-93d5-4e9b-bfdc-36c5c252efca@intel.com \
    --to=himal.prasad.ghimiray@intel.com \
    --cc=Thomas.Hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=oak.zeng@intel.com \
    --cc=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.