Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] Miscelaneous fixes for display tracepoints
Date: Thu, 29 Aug 2024 19:00:43 -0300	[thread overview]
Message-ID: <20240829220106.80449-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.

Gustavo Sousa (4):
  drm/i915/display: Fix out-of-bounds access in pipe-related 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    | 187 ++++++++++--------
 1 file changed, 106 insertions(+), 81 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-08-29 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 22:00 Gustavo Sousa [this message]
2024-08-29 22:00 ` [PATCH 1/4] drm/i915/display: Fix out-of-bounds access in pipe-related tracepoints Gustavo Sousa
2024-09-18 22:13   ` Matt Roper
2024-08-29 22:00 ` [PATCH 2/4] drm/i915/display: Store pipe name in trace events Gustavo Sousa
2024-09-18 22:37   ` Matt Roper
2024-09-23 14:30     ` Gustavo Sousa
2024-08-29 22:00 ` [PATCH 3/4] drm/i915/display: Do not use ids from enum pipe in TP_printk() Gustavo Sousa
2024-09-18 22:41   ` Matt Roper
2024-08-29 22:00 ` [PATCH 4/4] drm/i915/display: Cover all possible pipes " Gustavo Sousa
2024-09-18 22:49   ` Matt Roper
2024-09-23 16:55     ` Gustavo Sousa
2024-08-30  0:02 ` ✗ Fi.CI.CHECKPATCH: warning for Miscelaneous fixes for display tracepoints Patchwork
2024-08-30  0:09 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-31 13:52 ` ✗ Fi.CI.IGT: 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=20240829220106.80449-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox