mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] trace-cmd: quiet some output when using libtracecmd
@ 2015-12-04 15:37 Josef Bacik
  2016-02-23 22:23 ` Steven Rostedt
  0 siblings, 1 reply; 2+ messages in thread
From: Josef Bacik @ 2015-12-04 15:37 UTC (permalink / raw)
  To: rostedt, kernel-team, linux-kernel

If you link against libtracecmd you get a few extraneous warnings and printf's
that aren't related to your tool.  So by default make the path to the events you
are tracing use pr_stat() so if it's not defined we don't get the output, and
make the weak warning() do nothing by default.  The trace-cmd stuff has this
defined so it'll continue to work normally, it just won't be noisy for consumers
of libtracecmd.  Thanks,

Signed-off-by: Josef Bacik <jbacik@fb.com>
---
 parse-utils.c  | 5 -----
 trace-record.c | 2 +-
 2 files changed, 1 insertion(+), 6 deletions(-)

diff --git a/parse-utils.c b/parse-utils.c
index c5b0487..9f9c0e9 100644
--- a/parse-utils.c
+++ b/parse-utils.c
@@ -63,11 +63,6 @@ void __warning(const char *fmt, ...)
 
 void __weak warning(const char *fmt, ...)
 {
-	va_list ap;
-
-	va_start(ap, fmt);
-	__vwarning(fmt, ap);
-	va_end(ap);
 }
 
 void __vpr_stat(const char *fmt, va_list ap)
diff --git a/trace-record.c b/trace-record.c
index e4194b5..7d3ea37 100644
--- a/trace-record.c
+++ b/trace-record.c
@@ -2120,7 +2120,7 @@ static int expand_event_files(struct buffer_instance *instance,
 		path = globbuf.gl_pathv[i];
 
 		event = create_event(instance, path, old_event);
-		printf("%s\n", path);
+		pr_stat("%s\n", path);
 
 		len = strlen(path);
 
-- 
2.5.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] trace-cmd: quiet some output when using libtracecmd
  2015-12-04 15:37 [PATCH] trace-cmd: quiet some output when using libtracecmd Josef Bacik
@ 2016-02-23 22:23 ` Steven Rostedt
  0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2016-02-23 22:23 UTC (permalink / raw)
  To: Josef Bacik; +Cc: kernel-team, linux-kernel

On Fri, 4 Dec 2015 10:37:30 -0500
Josef Bacik <jbacik@fb.com> wrote:

> If you link against libtracecmd you get a few extraneous warnings and printf's
> that aren't related to your tool.  So by default make the path to the events you
> are tracing use pr_stat() so if it's not defined we don't get the output, and
> make the weak warning() do nothing by default.  The trace-cmd stuff has this
> defined so it'll continue to work normally, it just won't be noisy for consumers
> of libtracecmd.  Thanks,

I finally got around to look at these patches.

Applied!

-- Steve

> 
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
>  parse-utils.c  | 5 -----
>  trace-record.c | 2 +-
>  2 files changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/parse-utils.c b/parse-utils.c
> index c5b0487..9f9c0e9 100644
> --- a/parse-utils.c
> +++ b/parse-utils.c
> @@ -63,11 +63,6 @@ void __warning(const char *fmt, ...)
>  
>  void __weak warning(const char *fmt, ...)
>  {
> -	va_list ap;
> -
> -	va_start(ap, fmt);
> -	__vwarning(fmt, ap);
> -	va_end(ap);
>  }
>  
>  void __vpr_stat(const char *fmt, va_list ap)
> diff --git a/trace-record.c b/trace-record.c
> index e4194b5..7d3ea37 100644
> --- a/trace-record.c
> +++ b/trace-record.c
> @@ -2120,7 +2120,7 @@ static int expand_event_files(struct buffer_instance *instance,
>  		path = globbuf.gl_pathv[i];
>  
>  		event = create_event(instance, path, old_event);
> -		printf("%s\n", path);
> +		pr_stat("%s\n", path);
>  
>  		len = strlen(path);
>  

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-02-23 22:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-04 15:37 [PATCH] trace-cmd: quiet some output when using libtracecmd Josef Bacik
2016-02-23 22:23 ` Steven Rostedt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®