From: Steven Rostedt <rostedt@goodmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Jon Stanley <jonstanley@gmail.com>,
Sasha Levin <sasha.levin@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [libtraceevent] hrtimer_expire_entry unknown op '{'
Date: Tue, 5 Nov 2013 08:15:22 -0500 [thread overview]
Message-ID: <20131105081522.1c8e2012@gandalf.local.home> (raw)
In-Reply-To: <20131105093755.GB2272@swordfish.minsk.epam.com>
On Tue, 5 Nov 2013 12:37:55 +0300
Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> Hello,
>
> libtraceevent reports ` unknown op '{' ' while processing hrtimer_expire_entry event
Yes, we need to port the plugin code from trace-cmd to handle this and
other cases. It's a known issue.
-- Steve
>
> cat /sys/kernel/debug/tracing/events/timer/hrtimer_expire_entry/format
>
> name: hrtimer_expire_entry
> ID: 91
> 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:void * hrtimer; offset:8; size:8; signed:0;
> field:s64 now; offset:16; size:8; signed:1;
> field:void * function; offset:24; size:8; signed:0;
>
> print fmt: "hrtimer=%p function=%pf now=%llu", REC->hrtimer, REC->function, (unsigned long long)(((ktime_t) { .tv64 = REC->now }).tv64)
>
>
> -ss
next prev parent reply other threads:[~2013-11-05 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 9:37 Sergey Senozhatsky
2013-11-05 13:15 ` Steven Rostedt [this message]
2013-11-05 13:25 ` Sergey Senozhatsky
2013-11-12 21:31 ` Sergey Senozhatsky
2013-11-12 21:52 ` Steven Rostedt
2013-11-12 22:01 ` Sergey Senozhatsky
2013-11-12 23:04 ` Steven Rostedt
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=20131105081522.1c8e2012@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=jonstanley@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sasha.levin@oracle.com \
--cc=sergey.senozhatsky@gmail.com \
/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®