All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: event filtering with trace-cmd
Date: Wed, 12 Jun 2013 12:13:14 +0200	[thread overview]
Message-ID: <51B849BA.6000802@broadcom.com> (raw)

Hi Steven

I wanted to filter my debug events getting only one specific level. So I 
followed the instruction found online, but I get a parse error.

Running on 3.10-rc1 using trace-cmd 1.0.3. Should I upgrade?

Regards,
Arend
----8<-----------------------------------------------------------------
events/brcmfmac/brcmf_dbg# cat format
name: brcmf_dbg
ID: 1133
format: 

         field:unsigned short common_type;       offset:0;       size:2; 
signed:0;
         field:unsigned char common_flags;       offset:2;       size:1; 
signed:0;
         field:unsigned char common_preempt_count;       offset:3; 
  size:1; signed:0;
         field:int common_pid;   offset:4;       size:4; signed:1;

         field:u32 level;        offset:8;       size:4; signed:0;
         field:__data_loc char[] func;   offset:12;      size:4; signed:1;
         field:__data_loc char[] msg;    offset:16;      size:4; signed:1;
 

print fmt: "%s: %s", __get_str(func), __get_str(msg)

# sudo trace-cmd record -e brcmfmac:brcmf_dbg -f 'level & 0x40000'
disable all
enable brcmfmac:brcmf_dbg
path = /sys/kernel/debug/tracing/events/brcmfmac/brcmf_dbg/enable
(level & 0x40000)
^
parse_error: Invalid operator

trace-cmd: Invalid argument
   Failed filter of 
/sys/kernel/debug/tracing/events/brcmfmac/brcmf_dbg/filter


             reply	other threads:[~2013-06-12 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 10:13 Arend van Spriel [this message]
2013-06-12 16:22 ` event filtering with trace-cmd Steven Rostedt
2013-06-12 17:16   ` Steven Rostedt
2013-06-12 19:46     ` Arend van Spriel
2013-06-14  8:22     ` Arend van Spriel

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=51B849BA.6000802@broadcom.com \
    --to=arend@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.