From: Oak Zeng <oak.zeng@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Thomas.Hellstrom@linux.intel.com
Subject: [PATCH 2/3] drm/xe: Print vm flags in xe_vm trace print
Date: Thu, 28 Nov 2024 17:09:25 -0500 [thread overview]
Message-ID: <20241128220926.1826427-2-oak.zeng@intel.com> (raw)
In-Reply-To: <20241128220926.1826427-1-oak.zeng@intel.com>
Print vm flags in xe_vm trace print.
Signed-off-by: Oak Zeng <oak.zeng@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 3691897148c36..5600dff4f8189 100644
--- a/drivers/gpu/drm/xe/xe_trace_bo.h
+++ b/drivers/gpu/drm/xe/xe_trace_bo.h
@@ -185,16 +185,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-11-28 21:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 22:09 [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-11-28 22:09 ` Oak Zeng [this message]
2024-11-28 22:09 ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Oak Zeng
2024-11-28 23:39 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: trace bo create Patchwork
2024-11-28 23:39 ` ✓ CI.checkpatch: " Patchwork
2024-11-28 23:40 ` ✓ CI.KUnit: " Patchwork
2024-11-28 23:58 ` ✓ CI.Build: " Patchwork
2024-11-29 0:00 ` ✓ CI.Hooks: " Patchwork
2024-11-29 0:02 ` ✓ CI.checksparse: " Patchwork
2024-11-29 0:25 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-29 14:39 ` ✗ 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-12-18 16:48 [PATCH 0/3] drm/xe: Small trace print improvements 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
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=20241128220926.1826427-2-oak.zeng@intel.com \
--to=oak.zeng@intel.com \
--cc=Thomas.Hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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.