From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: francois.dugast@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v3 0/3] Port CPU-GPU timestamp correlation to XE KMD
Date: Wed, 4 Oct 2023 11:51:03 -0400 [thread overview]
Message-ID: <ZR2J57sjcPPZm7Gj@intel.com> (raw)
In-Reply-To: <20231003180909.3241390-1-umesh.nerlige.ramappa@intel.com>
On Tue, Oct 03, 2023 at 11:09:06AM -0700, Umesh Nerlige Ramappa wrote:
> This is a port of prior work from i915 to support fine-grained CPU-GPU
> timestamp correlation. Prior work is linked in this issue:
> https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/384
>
> Mesa and Perfetto are the consumers for this and the issue documents the
> need for higher accuracy in correlation.
>
> v2:
> - Change commit headers to fixup!
> - Fix kernel-doc errors
> - Include review comments
>
> v3:
> - s/rsvd/pad/ in struct drm_xe_engine_class_instance (Jose)
> - Initialize pad
Please do not push this series and sync with Francois. This should
be part of the big series that he is pushing soon. As soon as all
the UMDs are aligned there.
>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>
> Umesh Nerlige Ramappa (3):
> drm/xe: Fix array bounds check for queries
> drm/xe: Set the correct type for xe_to_user_engine_class
> drm/xe: Correlate engine and cpu timestamps with better accuracy
>
> drivers/gpu/drm/xe/xe_query.c | 147 +++++++++++++++++++++++++++++++++-
> include/uapi/drm/xe_drm.h | 104 ++++++++++++++++++------
> 2 files changed, 224 insertions(+), 27 deletions(-)
>
> --
> 2.38.1
>
prev parent reply other threads:[~2023-10-04 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:09 [Intel-xe] [PATCH v3 0/3] Port CPU-GPU timestamp correlation to XE KMD Umesh Nerlige Ramappa
2023-10-03 18:09 ` [Intel-xe] [PATCH v3 1/3] drm/xe: Fix array bounds check for queries Umesh Nerlige Ramappa
2023-10-03 18:09 ` [Intel-xe] [PATCH v3 2/3] drm/xe: Set the correct type for xe_to_user_engine_class Umesh Nerlige Ramappa
2023-10-03 18:09 ` [Intel-xe] [PATCH v3 3/3] drm/xe: Correlate engine and cpu timestamps with better accuracy Umesh Nerlige Ramappa
2023-10-03 18:12 ` [Intel-xe] ✓ CI.Patch_applied: success for Port CPU-GPU timestamp correlation to XE KMD Patchwork
2023-10-03 18:12 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-03 18:13 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-03 18:20 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 18:21 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 18:22 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 19:01 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-10-04 15:51 ` Rodrigo Vivi [this message]
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=ZR2J57sjcPPZm7Gj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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