From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Kieran Bingham <kbingham@kernel.org>, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 3/5] logger: Log to the FTrace buffer if tracing is enabled
Date: Fri, 25 Nov 2016 20:27:26 +0200 [thread overview]
Message-ID: <13232818.cNzCEhBpr4@avalon> (raw)
In-Reply-To: <b991400b-2429-c353-6629-f21c42b30f53@ideasonboard.com>
Hi Kieran,
On Friday 25 Nov 2016 18:10:10 Kieran Bingham wrote:
> On 25/11/16 17:40, Laurent Pinchart wrote:
> > On Friday 25 Nov 2016 13:59:14 Kieran Bingham wrote:
> >> From: Kieran Bingham <kieran@bingham.xyz>
> >>
> >> Extend the logger such that it will detect the tracing system, and also
> >> append print statement to this ring buffer.
> >>
> >> This provides the relevant logging output interspersed in the ftrace
> >> logs for an effective solution to identifying the actions that caused
> >> the traces to occur
> >>
> >> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
> >> ---
> >>
> >> scripts/logger.sh | 13 ++++++++++++-
> >> 1 file changed, 12 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/scripts/logger.sh b/scripts/logger.sh
> >> index 8123f0c9f6e3..8412b0ba9a08 100755
> >> --- a/scripts/logger.sh
> >> +++ b/scripts/logger.sh
> >> @@ -6,6 +6,17 @@ now() {
> >>
> >> label=${1:+ [$1]}
> >>
> >> +TRACE_MARKER=/sys/kernel/debug/tracing/trace_marker
> >> +if [ -e $TRACE_MARKER ]; then
> >> + extra_log_files=$TRACE_MARKER
> >> +fi
> >> +
> >>
> >> while read line ; do
> >>
> >> - echo "$(now)$label $line"
> >> + newline="$(now)$label $line"
> >> +
> >> + echo "$newline"
> >> +
> >> + for f in $extra_log_files; do
> >> + echo "$newline" >> $f;
> >
> > As the tracer adds a timestamp, should you echo "$label $line" only here ?
>
> Hrm, yes it is possibly a little bit redundant...
>
> My only argument would be that it will be a 'different' timestamp to the
> one logged by logger.sh.
>
> Inspection of a recent log shows a difference of around 40-50 ms, which
> will be the latency between capturing the time in $(now) and passing the
> buffer to the kernel.
>
> At this level though, the logger.sh is already susceptible to scheduler
> jitter anyway, so I'm not too worried about 40 ms. But anyone reading
> the logs will have to be aware of that extra latency.
If you think we should keep the timestamp I'm fine with that.
> >> + done;
> >>
> >> done
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-11-25 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 13:59 [PATCH 0/5] VSP-Tests: Add suspend resume tests and helpers Kieran Bingham
2016-11-25 13:59 ` [PATCH 1/5] scripts: Test suite runner Kieran Bingham
2016-11-25 18:21 ` Laurent Pinchart
2016-11-25 18:47 ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 2/5] scripts: Provide bin2png.sh helper Kieran Bingham
2016-11-25 17:55 ` Laurent Pinchart
2016-11-25 18:04 ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 3/5] logger: Log to the FTrace buffer if tracing is enabled Kieran Bingham
2016-11-25 17:40 ` Laurent Pinchart
2016-11-25 18:10 ` Kieran Bingham
2016-11-25 18:27 ` Laurent Pinchart [this message]
2016-11-25 13:59 ` [PATCH 4/5] tests: Test suspend/resume on idle pipelines Kieran Bingham
2016-11-25 17:13 ` Laurent Pinchart
2016-11-25 18:14 ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 5/5] tests: Test suspend/resume on active pipelines Kieran Bingham
2016-11-25 17:10 ` Laurent Pinchart
2016-11-25 18:40 ` Kieran Bingham
2016-11-25 19:03 ` Laurent Pinchart
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=13232818.cNzCEhBpr4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=kbingham@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.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