From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH v3] libtracefs: Add new API for open trace marker file
Date: Fri, 9 Apr 2021 16:47:25 +0300 [thread overview]
Message-ID: <CAPpZLN6s1_XHYbBUmDwSeCEAk_M-ec2FXnf-F1kH3q6mOaWzGA@mail.gmail.com> (raw)
In-Reply-To: <20210409091215.03ceca3d@gandalf.local.home>
On Fri, Apr 9, 2021 at 4:12 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 9 Apr 2021 07:27:39 +0300
> "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
>
> > Added new APIs for working with trace marker files of given instance.
> > Write strings in the trace_marker file:
> > tracefs_print_init();
> > tracefs_printf();
> > tracefs_vprintf();
> > tracefs_print_close();
> > Write binary data in trace_marker_raw file:
> > tracefs_binary_init();
> > tracefs_binary_write();
> > tracefs_binary_close();
>
> Thanks Tzvetomir, this looks exactly like what I wanted.
>
> A few nits with the code, but I may take this series as is and then add
> these changes on top, since I want to get this library done this week. Let
> me know if you have any issues with what I plan on changing, or just let me
> know if you are OK with it.
I'm OK with these changes. I was wondering about using a mutex to
protect the open, close and write, but decided to wait for your
changes that introduce the mutex and then to reuse it.
[ ... ]
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center
next prev parent reply other threads:[~2021-04-09 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 4:27 [PATCH v3] libtracefs: Add new API for open trace marker file Tzvetomir Stoyanov (VMware)
2021-04-09 13:12 ` Steven Rostedt
2021-04-09 13:47 ` Tzvetomir Stoyanov [this message]
2021-04-09 13:59 ` 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=CAPpZLN6s1_XHYbBUmDwSeCEAk_M-ec2FXnf-F1kH3q6mOaWzGA@mail.gmail.com \
--to=tz.stoyanov@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).