From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH v2 0/5] Miscelaneous fixes for display tracepoints
Date: Mon, 23 Sep 2024 16:02:49 -0300 [thread overview]
Message-ID: <20240923190324.83013-1-gustavo.sousa@intel.com> (raw)
I recently bumped into some issues while using trace-cmd to inspect i915
display trace events. This series of patches provides fixes for them.
v2:
- Add another patch to zero-initialize frame/scanline counts.
- Add static_assert(PIPE_A == _TRACE_PIPE_A) in "Do not use ids from enum pipe
in TP_printk()".
Gustavo Sousa (5):
drm/i915/display: Fix out-of-bounds access in pipe-related tracepoints
drm/i915/display: Zero-initialize frame/scanline counts in tracepoints
drm/i915/display: Store pipe name in trace events
drm/i915/display: Do not use ids from enum pipe in TP_printk()
drm/i915/display: Cover all possible pipes in TP_printk()
.../drm/i915/display/intel_display_trace.h | 206 +++++++++++-------
1 file changed, 125 insertions(+), 81 deletions(-)
--
2.46.1
next reply other threads:[~2024-09-23 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 19:02 Gustavo Sousa [this message]
2024-09-23 19:02 ` [PATCH v2 1/5] drm/i915/display: Fix out-of-bounds access in pipe-related tracepoints Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 2/5] drm/i915/display: Zero-initialize frame/scanline counts in tracepoints Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 3/5] drm/i915/display: Store pipe name in trace events Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 4/5] drm/i915/display: Do not use ids from enum pipe in TP_printk() Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 5/5] drm/i915/display: Cover all possible pipes " Gustavo Sousa
2024-09-23 19:23 ` Ville Syrjälä
2024-09-23 20:06 ` Gustavo Sousa
2024-09-23 20:18 ` Ville Syrjälä
2024-09-23 20:47 ` Gustavo Sousa
2024-09-23 20:48 ` Gustavo Sousa
2024-09-23 21:08 ` Ville Syrjälä
2024-09-26 19:26 ` ✗ Fi.CI.CHECKPATCH: warning for Miscelaneous fixes for display tracepoints (rev2) Patchwork
2024-09-26 19:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-04 11:12 ` Gustavo Sousa
2024-10-04 11:33 ` Jani Nikula
2024-10-04 11:43 ` Gustavo Sousa
2024-10-04 12:03 ` Saarinen, Jani
2024-10-04 12:09 ` Saarinen, Jani
2024-10-08 19:46 ` ✗ Fi.CI.CHECKPATCH: warning for Miscelaneous fixes for display tracepoints (rev3) Patchwork
2024-10-08 19:55 ` ✗ Fi.CI.BAT: failure " Patchwork
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=20240923190324.83013-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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