mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Don't set wildcard filter for non-existing module
Date: Tue, 3 Oct 2017 17:44:38 -0400	[thread overview]
Message-ID: <20171003174438.6aeb107e@gandalf.local.home> (raw)
In-Reply-To: <4b13012c-8b08-8eb4-2cbd-0abdd1699af6@siemens.com>

On Thu, 28 Sep 2017 13:11:40 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:

> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> If filter_mod is NULL, there is no need to add it to the list. This
> avoids premature termination of trace-cmd on systems without
> CONFIG_DYNAMIC_FTRACE.

Thanks, and it also fixes setting all functions needlessly being set in
the filter.

 # trace-cmd record -p function cat /sys/kernel/tracing/set_ftrace_filter | head
  plugin 'function'
initcall_blacklisted
run_init_process
try_to_run_init_process
do_one_initcall
rootfs_mount
name_to_dev_t
match_dev_by_uuid
init_linuxrc
bstat
calibration_delay_done
CPU0 data recorded at offset=0x446000
    1515520 bytes in size
CPU1 data recorded at offset=0x5b8000
    1540096 bytes in size
CPU2 data recorded at offset=0x730000
    1527808 bytes in size
CPU3 data recorded at offset=0x8a5000
    1540096 bytes in size

When it should be:

# trace-cmd record -p function cat /debug/tracing/set_ftrace_filter |head
  plugin 'function'
#### all functions enabled ####
CPU0 data recorded at offset=0x446000
    1605632 bytes in size
CPU1 data recorded at offset=0x5ce000
    1478656 bytes in size
CPU2 data recorded at offset=0x737000
    1601536 bytes in size
CPU3 data recorded at offset=0x8be000
    1576960 bytes in size
CPU 0: 8600 events lost
CPU 1: 5705 events lost
CPU 2: 920 events lost
CPU 3: 2225 events lost

-- Steve


> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  trace-record.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/trace-record.c b/trace-record.c
> index 020a373..a0b6541 100644
> --- a/trace-record.c
> +++ b/trace-record.c
> @@ -4680,7 +4680,7 @@ void trace_record (int argc, char **argv)
>  		}
>  	}
>  
> -	if (!filtered)
> +	if (!filtered && instance->filter_mod)
>  		add_func(&instance->filter_funcs,
>  			 instance->filter_mod, "*");
>  

      reply	other threads:[~2017-10-03 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 11:11 Jan Kiszka
2017-10-03 21:44 ` Steven Rostedt [this message]

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=20171003174438.6aeb107e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®