From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs: Add API to set custom tracing directory
Date: Thu, 8 Sep 2022 19:31:20 -0400 [thread overview]
Message-ID: <20220908193120.7a85549e@gandalf.local.home> (raw)
In-Reply-To: <20220826054212.146976-1-tz.stoyanov@gmail.com>
On Fri, 26 Aug 2022 08:42:12 +0300
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> Usually the system's tracing directory is mounted as a subfolder in
> /sys/kernel and is auto detected by the tracefs library, using the
> information from the "/proc/mounts" file. But there are cases where
> /sys and /proc are mounted inside a container on a custom mount point.
> In those cases the tracefs library cannot auto detect the system's
> tracing directory. That's why a new API is introduced, to handle these
> custom use cases:
> int tracefs_set_tracing_dir(char *tracing_dir);
>
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
Applied. Thanks Tzvetomir!
-- Steve
prev parent reply other threads:[~2022-09-08 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 5:42 [PATCH] libtracefs: Add API to set custom tracing directory Tzvetomir Stoyanov (VMware)
2022-09-08 23:31 ` 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=20220908193120.7a85549e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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;
as well as URLs for NNTP newsgroup(s).