Intel-XE Archive on 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 2/3] drm/xe: Print vm flags in xe_vm trace print
Date: Mon, 23 Dec 2024 15:55:42 +0530	[thread overview]
Message-ID: <656c5722-1443-4ca0-a0ec-46ce1e08c020@intel.com> (raw)
In-Reply-To: <20241218164833.2364049-3-oak.zeng@intel.com>



On 18-12-2024 22:18, Oak Zeng wrote:
> Print vm flags in xe_vm trace print. This is helpful
> to diagnosis the VM mode of operation.
> 
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_trace_bo.h | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_trace_bo.h b/drivers/gpu/drm/xe/xe_trace_bo.h
> index 53807f2ef4808..a46f7cfd92c6f 100644
> --- a/drivers/gpu/drm/xe/xe_trace_bo.h
> +++ b/drivers/gpu/drm/xe/xe_trace_bo.h
> @@ -190,16 +190,19 @@ DECLARE_EVENT_CLASS(xe_vm,
>   			     __string(dev, __dev_name_vm(vm))
>   			     __field(struct xe_vm *, vm)
>   			     __field(u32, asid)
> +			     __field(u32, flags)
>   			     ),
>   
>   		    TP_fast_assign(
>   			   __assign_str(dev);
>   			   __entry->vm = vm;
>   			   __entry->asid = vm->usm.asid;
> +			   __entry->flags = vm->flags;
>   			   ),
>   
> -		    TP_printk("dev=%s, vm=%p, asid=0x%05x", __get_str(dev),
> -			      __entry->vm, __entry->asid)
> +		    TP_printk("dev=%s, vm=%p, asid=0x%05x, vm flags=0x%05x",
> +			      __get_str(dev), __entry->vm, __entry->asid,
> +			      __entry->flags)

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

>   );
>   
>   DEFINE_EVENT(xe_vm, xe_vm_kill,


  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
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 [this message]
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 2/3] drm/xe: Print vm flags in xe_vm trace print Oak Zeng
2024-12-18  3:04   ` Matthew Brost
2024-11-28 22:09 [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-11-28 22:09 ` [PATCH 2/3] drm/xe: Print vm flags in xe_vm trace print 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=656c5722-1443-4ca0-a0ec-46ce1e08c020@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox