linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: christopher lee <christopher.lee.eu@gmail.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: how to register an event handler for the instance
Date: Sat, 7 May 2022 08:02:39 +0300	[thread overview]
Message-ID: <CAPpZLN4A8tes3tnzDqLFBT7S2SvBixFwDW7GkYbSPeA+3e1yCQ@mail.gmail.com> (raw)
In-Reply-To: <93fd065420c6a04141b5e8ba9c89dae1e7c9b6a0.camel@gmail.com>

On Fri, May 6, 2022 at 7:18 PM christopher lee
<christopher.lee.eu@gmail.com> wrote:
>
> Hi all,
>
> I use libtraceevent in my trace tool to parse the event log. Now I
> allocated an instance, but no idea how to use
> tep_register_event_handler() to register a handler for the instance. Is
> it possilbe to register handler for the event in the instance?
>

Hi Chrit,
All trace events are the same across all trace instances, thus the
handler registered with tep_register_event_handler() handles events
from all instances with a given id. That's why there are no "instance"
oriented APIs in that library. I would suggest looking at the tracefs
library, which is instance aware. It can be used to allocate trace
instances and read events from a given instance.

https://trace-cmd.org/Documentation/libtracefs/

> https://trace-cmd.org/Documentation/libtraceevent/libtraceevent-reg_event_handler.html
>
> thanks for any information.
>
> Best regards,
> Chrit



-- 
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center

  reply	other threads:[~2022-05-07  5:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 16:18 how to register an event handler for the instance christopher lee
2022-05-07  5:02 ` Tzvetomir Stoyanov [this message]
2022-05-11 18:33   ` christopher lee
2022-05-12  3:05     ` Tzvetomir Stoyanov
2022-05-16 18:14     ` Steven Rostedt
2022-05-16 21:24       ` christopher lee

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=CAPpZLN4A8tes3tnzDqLFBT7S2SvBixFwDW7GkYbSPeA+3e1yCQ@mail.gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=christopher.lee.eu@gmail.com \
    --cc=linux-trace-devel@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).