From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
Wade Farnsworth <wade_farnsworth@mentor.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] v4l2-dev: Add tracepoints for QBUF and DQBUF
Date: Tue, 10 Dec 2013 18:53:59 -0200 [thread overview]
Message-ID: <20131210185359.49f3f020@samsung.com> (raw)
In-Reply-To: <5290DDD8.7070305@xs4all.nl>
Em Sat, 23 Nov 2013 17:54:48 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> On 11/23/2013 05:30 PM, Sylwester Nawrocki wrote:
> > Hi,
> >
> > On 11/23/2013 12:25 PM, Hans Verkuil wrote:
> >> Hi Wade,
> >>
> >> On 11/22/2013 08:48 PM, Wade Farnsworth wrote:
> >>> Add tracepoints to the QBUF and DQBUF ioctls to enable rudimentary
> >>> performance measurements using standard kernel tracers.
> >>>
> >>> Signed-off-by: Wade Farnsworth<wade_farnsworth@mentor.com>
> >>> ---
> >>>
> >>> This is the update to the RFC patch I posted a few weeks back. I've added
> >>> several bits of metadata to the tracepoint output per Mauro's suggestion.
> >>
> >> I don't like this. All v4l2 ioctls can already be traced by doing e.g.
> >> echo 1 (or echo 2)>/sys/class/video4linux/video0/debug.
> >>
> >> So this code basically duplicates that functionality. It would be nice to be able
> >> to tie in the existing tracing code (v4l2-ioctl.c) into tracepoints.
> >
> > I think it would be really nice to have this kind of support for standard
> > traces at the v4l2 subsystem. Presumably it could even gradually replace
> > the v4l2 custom debug infrastructure.
> >
> > If I understand things correctly, the current tracing/profiling
> > infrastructure
> > is much less invasive than inserting printks all over, which may cause
> > changes
> > in control flow. I doubt the system could be reliably profiled by
> > enabling all
> > those debug prints.
> >
> > So my vote would be to add support for standard tracers, like in other
> > subsystems in the kernel.
>
> The reason for the current system is to trace which ioctls are called in
> what order by a misbehaving application. It's very useful for that,
> especially when trying to debug user problems.
>
> I don't mind switching to tracepoints as long as this functionality is
> kept one way or another.
I agree with Sylwester: we should move to tracepoints, and this is a good
start.
Regards,
Mauro
next prev parent reply other threads:[~2013-12-10 20:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 15:03 [RFC][PATCH] v4l2-dev: Add tracepoints for QBUF and DQBUF Wade Farnsworth
2013-10-31 13:29 ` Mauro Carvalho Chehab
2013-11-22 19:48 ` [PATCH] " Wade Farnsworth
2013-11-23 11:25 ` Hans Verkuil
2013-11-23 16:30 ` Sylwester Nawrocki
2013-11-23 16:54 ` Hans Verkuil
2013-12-10 20:53 ` Mauro Carvalho Chehab [this message]
2013-12-11 7:29 ` Hans Verkuil
2013-12-11 10:44 ` Mauro Carvalho Chehab
2013-12-11 11:53 ` Hans Verkuil
2013-12-11 12:44 ` Mauro Carvalho Chehab
2013-12-11 13:15 ` Hans Verkuil
2013-12-11 13:46 ` Mauro Carvalho Chehab
2013-12-11 14:53 ` Wade Farnsworth
2013-12-12 8:00 ` Hans Verkuil
2013-12-12 14:27 ` Wade Farnsworth
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=20131210185359.49f3f020@samsung.com \
--to=m.chehab@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sylvester.nawrocki@gmail.com \
--cc=wade_farnsworth@mentor.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