From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] drm/i915: Silence pipe tracepoint WARNs
Date: Fri, 5 Mar 2021 17:38:03 +0200 [thread overview]
Message-ID: <YEJQW6UHGEaeET8U@intel.com> (raw)
In-Reply-To: <20210304142022.5d266e3b@gandalf.local.home>
On Thu, Mar 04, 2021 at 02:20:22PM -0500, Steven Rostedt wrote:
> On Thu, 4 Mar 2021 19:04:17 +0200
> Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
>
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > I believe this should silence the WARN spew from the
> > pipe disable tracepoint Steve reported. And I tossed in
> > a few other minor improvements as well.
> >
> > Cc: Steven Rostedt <rostedt@goodmis.org>
>
> It seemed to have stopped the general protection faults when tracing all
> events on my machine.
>
> Reported-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Series pushed to drm-intel-next. Thanks for reporting the problem.
>
> -- Steve
>
> >
> > Ville Syrjälä (4):
> > drm/i915: Move pipe enable/disable tracepoints to
> > intel_crtc_vblank_{on,off}()
> > drm/i915: Don't try to query the frame counter for disabled pipes
> > drm/i915: Return zero as the scanline counter for disabled pipes
> > drm/i915: Fix DSI TE max_vblank_count handling
> >
> > drivers/gpu/drm/i915/display/intel_crtc.c | 24 +++++++++++++++++---
> > drivers/gpu/drm/i915/display/intel_display.c | 8 +------
> > drivers/gpu/drm/i915/i915_irq.c | 2 +-
> > 3 files changed, 23 insertions(+), 11 deletions(-)
> >
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-05 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:04 [Intel-gfx] [PATCH 0/4] drm/i915: Silence pipe tracepoint WARNs Ville Syrjala
2021-03-04 17:04 ` [Intel-gfx] [PATCH 1/4] drm/i915: Move pipe enable/disable tracepoints to intel_crtc_vblank_{on, off}() Ville Syrjala
2021-03-04 17:04 ` [Intel-gfx] [PATCH 2/4] drm/i915: Don't try to query the frame counter for disabled pipes Ville Syrjala
2021-03-04 17:04 ` [Intel-gfx] [PATCH 3/4] drm/i915: Return zero as the scanline " Ville Syrjala
2021-03-04 17:04 ` [Intel-gfx] [PATCH 4/4] drm/i915: Fix DSI TE max_vblank_count handling Ville Syrjala
2021-03-04 17:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Silence pipe tracepoint WARNs Patchwork
2021-03-04 19:20 ` [Intel-gfx] [PATCH 0/4] " Steven Rostedt
2021-03-05 15:38 ` Ville Syrjälä [this message]
2021-03-04 23:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2021-03-05 8:45 ` [Intel-gfx] [PATCH 0/4] " Jani Nikula
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=YEJQW6UHGEaeET8U@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rostedt@goodmis.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