linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] tools lib traceevent: Remove extra '\n' in print_event_time()
Date: Wed, 4 Mar 2020 09:59:40 -0300	[thread overview]
Message-ID: <20200304125940.GA6498@redhat.com> (raw)
In-Reply-To: <20200303231852.6ab6882f@oasis.local.home>

Em Tue, Mar 03, 2020 at 11:18:52PM -0500, Steven Rostedt escreveu:
> 
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
> 
> If the precesion of print_event_time() is zero or greater than the

precision, right?

Thanks, applied.

- Arnaldo

> timestamp, it uses a different format. But that format had an extra new line
> at the end, and caused the output to not look right:
> 
> cpus=2
>            sleep-3946  [001]111264306005
> : function:             inotify_inode_queue_event
>            sleep-3946  [001]111264307158
> : function:             __fsnotify_parent
>            sleep-3946  [001]111264307637
> : function:             inotify_dentry_parent_queue_event
>            sleep-3946  [001]111264307989
> : function:             fsnotify
>            sleep-3946  [001]111264308401
> : function:             audit_syscall_exit
> 
> Fixes: 38847db9740a ("libtraceevent, perf tools: Changes in tep_print_event_* APIs")
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
>  tools/lib/traceevent/event-parse.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
> index beaa8b8c08ff..e1bd2a93c6db 100644
> --- a/tools/lib/traceevent/event-parse.c
> +++ b/tools/lib/traceevent/event-parse.c
> @@ -5541,7 +5541,7 @@ static void print_event_time(struct tep_handle *tep, struct trace_seq *s,
>  	if (p10 > 1 && p10 < time)
>  		trace_seq_printf(s, "%5llu.%0*llu", time / p10, prec, time % p10);
>  	else
> -		trace_seq_printf(s, "%12llu\n", time);
> +		trace_seq_printf(s, "%12llu", time);
>  }
>  
>  struct print_event_type {
> -- 
> 2.20.1


  reply	other threads:[~2020-03-04 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  4:18 [PATCH] tools lib traceevent: Remove extra '\n' in print_event_time() Steven Rostedt
2020-03-04 12:59 ` Arnaldo Carvalho de Melo [this message]
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for Steven Rostedt (VMware)

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=20200304125940.GA6498@redhat.com \
    --to=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).