From: Matthew Brost <matthew.brost@intel.com>
To: Oak Zeng <oak.zeng@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<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: Tue, 17 Dec 2024 19:04:41 -0800 [thread overview]
Message-ID: <Z2I7ycwlr+pIeC5n@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20241217231420.2361302-3-oak.zeng@intel.com>
On Tue, Dec 17, 2024 at 06:14:19PM -0500, Oak Zeng wrote:
> Print vm flags in xe_vm trace print.
>
I was told we should try to have better commit messages. Maybe add why
this useful. e.g., Flags help diagnosis the VM mode of operation.
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
With a better commit message:
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)
> );
>
> DEFINE_EVENT(xe_vm, xe_vm_kill,
> --
> 2.26.3
>
next prev parent reply other threads:[~2024-12-18 3:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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-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 [this message]
2024-12-17 23:14 ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Oak Zeng
2024-12-18 3:09 ` Matthew Brost
2024-12-18 2:04 ` ✓ CI.Patch_applied: success for drm/xe: Small trace print improvements Patchwork
2024-12-18 2:04 ` ✓ CI.checkpatch: " Patchwork
2024-12-18 2:05 ` ✓ CI.KUnit: " Patchwork
2024-12-18 2:23 ` ✓ CI.Build: " Patchwork
2024-12-18 2:26 ` ✓ CI.Hooks: " Patchwork
2024-12-18 2:27 ` ✓ CI.checksparse: " Patchwork
2024-12-18 3:01 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-18 12:58 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-12-18 16:48 [PATCH 0/3] " Oak Zeng
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-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=Z2I7ycwlr+pIeC5n@lstrano-desk.jf.intel.com \
--to=matthew.brost@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