All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH 1/3] drm/i915: Fix various tracepoints for gen2
Date: Tue, 18 Jun 2019 18:14:00 +0300	[thread overview]
Message-ID: <20190618151400.GO5942@intel.com> (raw)
In-Reply-To: <156086918982.31375.16222108074150558958@skylake-alporthouse-com>

On Tue, Jun 18, 2019 at 03:46:29PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-06-18 15:21:06)
> > @@ -59,14 +57,13 @@ TRACE_EVENT(intel_pipe_disable,
> >                              ),
> >  
> >             TP_fast_assign(
> > -                          enum pipe _pipe;
> > -                          for_each_pipe(dev_priv, _pipe) {
> > -                                  __entry->frame[_pipe] =
> > -                                          dev_priv->drm.driver->get_vblank_counter(&dev_priv->drm, _pipe);
> > -                                  __entry->scanline[_pipe] =
> > -                                          intel_get_crtc_scanline(intel_get_crtc_for_pipe(dev_priv, _pipe));
> > +                          struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
> > +                          struct intel_crtc *_crtc;
> > +                          for_each_intel_crtc(&dev_priv->drm, _crtc) {
> > +                                  __entry->frame[_crtc->pipe] = intel_crtc_get_vblank_counter(_crtc);
> > +                                  __entry->scanline[_crtc->pipe] = intel_get_crtc_scanline(_crtc);
> >                            }
> > -                          __entry->pipe = pipe;
> > +                          __entry->pipe = crtc->pipe;
> 
> Ok. Stared hard to make sure it was _crtc and not crtc. Would crtc__ be
> more obvious, or maybe it__ so that it doesn't look anything like the
> crtc argument.

I suppose a more distinct name might be a good idea.

> 
> >             TP_fast_assign(
> > -                          enum pipe pipe;
> > -                          for_each_pipe(dev_priv, pipe) {
> > -                                  __entry->frame[pipe] =
> > -                                          dev_priv->drm.driver->get_vblank_counter(&dev_priv->drm, pipe);
> > -                                  __entry->scanline[pipe] =
> > -                                          intel_get_crtc_scanline(intel_get_crtc_for_pipe(dev_priv, pipe));
> > +                          struct intel_crtc *crtc;
> > +                          for_each_intel_crtc(&dev_priv->drm, crtc) {
> > +                                  __entry->frame[crtc->pipe] = intel_crtc_get_vblank_counter(crtc);
> > +                                  __entry->scanline[crtc->pipe] = intel_get_crtc_scanline(crtc);
> >                            }
> 
> Or even a populate_vblanks(i915, __entry->frame, __entry->scanline)
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-18 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 14:21 [PATCH 0/3] drm/i915: Finish drm_driver vfunc cleanup Ville Syrjala
2019-06-18 14:21 ` [PATCH 1/3] drm/i915: Fix various tracepoints for gen2 Ville Syrjala
2019-06-18 14:46   ` Chris Wilson
2019-06-18 15:14     ` Ville Syrjälä [this message]
2019-06-18 14:21 ` [PATCH 2/3] drm/i915: Nuke drm_driver irq vfuncs Ville Syrjala
2019-06-18 14:54   ` Chris Wilson
2019-06-18 15:26     ` Ville Syrjälä
2019-06-18 14:21 ` [PATCH 3/3] drm/i915: Initialize drm_driver vblank funcs at compile time Ville Syrjala
2019-06-18 14:55   ` Chris Wilson
2019-06-19 16:18     ` Ville Syrjälä
2019-06-18 15:12 ` ✗ Fi.CI.BAT: failure for drm/i915: Finish drm_driver vfunc cleanup 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=20190618151400.GO5942@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shawn.guo@linaro.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 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.