From: Daniel Vetter <daniel@ffwll.ch>
To: Heinrich Fink <heinrich.fink@daqri.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm: Add high-precision time to vblank trace event
Date: Tue, 3 Sep 2019 11:52:58 +0200 [thread overview]
Message-ID: <20190903095258.GS2112@phenom.ffwll.local> (raw)
In-Reply-To: <CAB6MLDY3q_w2Gv+x3mjriFjGvg0BuJk3w-1pJ8xfEg_3m+q90w@mail.gmail.com>
On Tue, Sep 03, 2019 at 11:19:19AM +0200, Heinrich Fink wrote:
> On Tue, 3 Sep 2019 at 09:46, Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Mon, Sep 02, 2019 at 04:24:12PM +0200, Heinrich Fink wrote:
> > > Store the timestamp of the current vblank in the new field 'time' of the
> > > vblank trace event. If the timestamp is calculated by a driver that
> > > supports high-precision vblank timing, set the field 'high-prec' to
> > > 'true'.
> > >
> > > User space can now access actual hardware vblank times via the tracing
> > > infrastructure. Tracing applications (such as GPUVis, see [0] for
> > > related discussion), can use the newly added information to conduct a
> > > more accurate analysis of display timing.
> > >
> > > v2 Fix author name (missing last name)
> > >
> > > [0] https://github.com/mikesart/gpuvis/issues/30
> > >
> > > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Signed-off-by: Heinrich Fink <heinrich.fink@daqri.com>
> >
> > Applied, thanks.
>
> thanks! One question: After sending v2, I got an email from patchwork
> pointing at some failed style checks (CHECK:PARENTHESIS_ALIGNMENT,
> CHECK:COMPARISON_TO_NULL). Just so I know for the future, are these
> checks mandatory to be addressed? I haven't had a chance to address
> them yet. FWIW, linux-tree/scripts/checkpatch.pl did not complain.
It's the same script, but I think CI uses some different options/flags. I
generally ignore these, but also generally good to stick to the style.
$ dim checkpatch
in our maintainer-tools should give you the drm flavoured checkpatch.
-Daniel
>
> - Heinrich
>
> > -Daniel
> >
> > > ---
> > > drivers/gpu/drm/drm_trace.h | 14 ++++++++++----
> > > drivers/gpu/drm/drm_vblank.c | 3 ++-
> > > 2 files changed, 12 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/drm_trace.h b/drivers/gpu/drm/drm_trace.h
> > > index 471eb927474b..11c6dd577e8e 100644
> > > --- a/drivers/gpu/drm/drm_trace.h
> > > +++ b/drivers/gpu/drm/drm_trace.h
> > > @@ -13,17 +13,23 @@ struct drm_file;
> > > #define TRACE_INCLUDE_FILE drm_trace
> > >
> > > TRACE_EVENT(drm_vblank_event,
> > > - TP_PROTO(int crtc, unsigned int seq),
> > > - TP_ARGS(crtc, seq),
> > > + TP_PROTO(int crtc, unsigned int seq, ktime_t time, bool high_prec),
> > > + TP_ARGS(crtc, seq, time, high_prec),
> > > TP_STRUCT__entry(
> > > __field(int, crtc)
> > > __field(unsigned int, seq)
> > > + __field(ktime_t, time)
> > > + __field(bool, high_prec)
> > > ),
> > > TP_fast_assign(
> > > __entry->crtc = crtc;
> > > __entry->seq = seq;
> > > - ),
> > > - TP_printk("crtc=%d, seq=%u", __entry->crtc, __entry->seq)
> > > + __entry->time = time;
> > > + __entry->high_prec = high_prec;
> > > + ),
> > > + TP_printk("crtc=%d, seq=%u, time=%lld, high-prec=%s",
> > > + __entry->crtc, __entry->seq, __entry->time,
> > > + __entry->high_prec ? "true" : "false")
> > > );
> > >
> > > TRACE_EVENT(drm_vblank_event_queued,
> > > diff --git a/drivers/gpu/drm/drm_vblank.c b/drivers/gpu/drm/drm_vblank.c
> > > index fd1fbc77871f..c99feda25dea 100644
> > > --- a/drivers/gpu/drm/drm_vblank.c
> > > +++ b/drivers/gpu/drm/drm_vblank.c
> > > @@ -1731,7 +1731,8 @@ static void drm_handle_vblank_events(struct drm_device *dev, unsigned int pipe)
> > > send_vblank_event(dev, e, seq, now);
> > > }
> > >
> > > - trace_drm_vblank_event(pipe, seq);
> > > + trace_drm_vblank_event(pipe, seq, now,
> > > + dev->driver->get_vblank_timestamp != NULL);
> > > }
> > >
> > > /**
> > > --
> > > 2.23.0.rc1
> > >
> >
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > http://blog.ffwll.ch
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-03 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190809153639.14193-1-heinrich.fink@daqri.com>
2019-08-14 17:15 ` [PATCH] drm: Add high-precision time to vblank trace event Daniel Vetter
2019-09-02 14:24 ` Heinrich Fink
2019-09-02 14:24 ` [PATCH v2] " Heinrich Fink
2019-09-03 7:46 ` Daniel Vetter
2019-09-03 9:19 ` Heinrich Fink
2019-09-03 9:52 ` Daniel Vetter [this message]
2019-09-21 8:33 ` Heinrich Fink
2019-09-23 12:05 ` Daniel Vetter
2019-09-23 14:09 ` Heinrich Fink
2019-09-02 14:40 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-09-02 15:04 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-02 16: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=20190903095258.GS2112@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heinrich.fink@daqri.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