From: Oak Zeng <oak.zeng@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Thomas.Hellstrom@linux.intel.com, rodrigo.vivi@intel.com
Subject: [PATCH 0/3] drm/xe: Small trace print improvements
Date: Wed, 18 Dec 2024 11:48:30 -0500 [thread overview]
Message-ID: <20241218164833.2364049-1-oak.zeng@intel.com> (raw)
1. Trace bo create
2. Print vm flags in xe_vm trace print
3. Print vm parameter in xe_vma trace
Oak Zeng (3):
drm/xe: trace bo create
drm/xe: Print vm flags in xe_vm trace print
drm/xe: Print vm parameter in xe_vma trace
drivers/gpu/drm/xe/xe_bo.c | 1 +
drivers/gpu/drm/xe/xe_trace_bo.h | 19 +++++++++++++++----
2 files changed, 16 insertions(+), 4 deletions(-)
--
2.26.3
next reply other threads:[~2024-12-18 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 16:48 Oak Zeng [this message]
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
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
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=20241218164833.2364049-1-oak.zeng@intel.com \
--to=oak.zeng@intel.com \
--cc=Thomas.Hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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.