Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Atwood <matthew.s.atwood@intel.com>
To: Stuart Summers <stuart.summers@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <matthew.brost@intel.com>,
	<niranjana.vishwanathapura@intel.com>, <zhanjun.dong@intel.com>,
	<shuicheng.lin@intel.com>
Subject: Re: [PATCH 3/6] drm/xe: Add the BO pointer info to the BO trace
Date: Tue, 28 Oct 2025 13:11:31 -0700	[thread overview]
Message-ID: <aQEjczSXGN4eM_43@msatwood-mobl> (raw)
In-Reply-To: <20251027180412.63743-4-stuart.summers@intel.com>

On Mon, Oct 27, 2025 at 06:04:09PM +0000, Stuart Summers wrote:
> Just a little extra detail to make BOs easier to track
> through the trace event log.
> 
Reviewed-by: Matt Atwood <matthew.s.atwood@intel.com>
> Signed-off-by: Stuart Summers <stuart.summers@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_trace_bo.h | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_trace_bo.h b/drivers/gpu/drm/xe/xe_trace_bo.h
> index 238311cfb816..0d795733e0f0 100644
> --- a/drivers/gpu/drm/xe/xe_trace_bo.h
> +++ b/drivers/gpu/drm/xe/xe_trace_bo.h
> @@ -27,6 +27,7 @@ DECLARE_EVENT_CLASS(xe_bo,
>  
>  		    TP_STRUCT__entry(
>  			     __string(dev, __dev_name_bo(bo))
> +			     __field(struct xe_bo *, bo)
>  			     __field(size_t, size)
>  			     __field(u32, flags)
>  			     __field(struct xe_vm *, vm)
> @@ -34,13 +35,14 @@ DECLARE_EVENT_CLASS(xe_bo,
>  
>  		    TP_fast_assign(
>  			   __assign_str(dev);
> +			   __entry->bo = bo;
>  			   __entry->size = xe_bo_size(bo);
>  			   __entry->flags = bo->flags;
>  			   __entry->vm = bo->vm;
>  			   ),
>  
> -		    TP_printk("dev=%s, size=%zu, flags=0x%02x, vm=%p",
> -			      __get_str(dev), __entry->size,
> +		    TP_printk("dev=%s, %p, size=%zu, flags=0x%02x, vm=%p",
> +			      __get_str(dev), __entry->bo, __entry->size,
>  			      __entry->flags, __entry->vm)
>  );
>  
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-10-28 20:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 18:04 [PATCH 0/6] Fix a couple of wedge corner-case memory leaks Stuart Summers
2025-10-27 18:04 ` [PATCH 1/6] drm/xe: Add additional trace points for LRCs Stuart Summers
2025-10-28 19:46   ` Matt Atwood
2025-10-28 20:11     ` Summers, Stuart
2025-10-27 18:04 ` [PATCH 2/6] drm/xe: Add a trace point for VM close Stuart Summers
2025-10-28 20:03   ` Matt Atwood
2025-10-28 20:10     ` Summers, Stuart
2025-10-27 18:04 ` [PATCH 3/6] drm/xe: Add the BO pointer info to the BO trace Stuart Summers
2025-10-28 20:11   ` Matt Atwood [this message]
2025-10-27 18:04 ` [PATCH 4/6] drm/xe: Add new exec queue trace points Stuart Summers
2025-10-28 20:29   ` Matt Atwood
2025-10-27 18:04 ` [PATCH 5/6] drm/xe: Correct migration VM teardown order Stuart Summers
2025-10-27 19:46   ` Matthew Brost
2025-10-27 18:04 ` [PATCH 6/6] drm/xe: Clean up GuC software state after a wedge Stuart Summers
2025-10-27 18:16 ` ✗ CI.checkpatch: warning for Fix a couple of wedge corner-case memory leaks (rev6) Patchwork
2025-10-27 18:17 ` ✗ CI.KUnit: failure " Patchwork
2025-10-27 18:18   ` Summers, Stuart
2025-10-27 20:10     ` Summers, Stuart
  -- strict thread matches above, loose matches on Subject: below --
2025-10-14 18:09 [PATCH 0/6] Fix a couple of wedge corner-case memory leaks Stuart Summers
2025-10-14 18:09 ` [PATCH 3/6] drm/xe: Add the BO pointer info to the BO trace Stuart Summers

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=aQEjczSXGN4eM_43@msatwood-mobl \
    --to=matthew.s.atwood@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=stuart.summers@intel.com \
    --cc=zhanjun.dong@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