From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 1/7] trace-cmd: Implemented new lib API: tracecmd_local_events_system()
Date: Mon, 21 Jan 2019 04:02:01 -0500 [thread overview]
Message-ID: <20190121040201.479f8ede@vmware.local.home> (raw)
In-Reply-To: <20190116191838.32127-2-tstoyanov@vmware.com>
On Wed, 16 Jan 2019 21:18:32 +0200
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> +static int tracecmd_fill_local_events_system(const char *tracing_dir,
> + struct tep_handle *pevent,
> + char *sys_name)
> {
> struct dirent *dent;
> char *events_dir;
> @@ -1189,7 +1161,8 @@ int tracecmd_fill_local_events(const char *tracing_dir, struct tep_handle *peven
> if (strcmp(name, ".") == 0 ||
> strcmp(name, "..") == 0)
> continue;
> -
> + if (sys_name && strcmp(name, sys_name))
Small nit. Please compare as: strcmp(name, sys_name) != 0
This to make it look like it is not equal. One of the flaws of the
"strcmp" is that a match is false and a non match is true, which makes
it likely to be done wrong :-p
If you noticed, the strcmp() in the previous if uses "== 0" as a way to
say "this is true on match"
> + continue;
> sys = append_file(events_dir, name);
> ret = stat(sys, &st);
> if (ret < 0 || !S_ISDIR(st.st_mode)) {
> @@ -1217,6 +1190,58 @@ int tracecmd_fill_local_events(const char *tracing_dir, struct tep_handle *peven
> return ret;
> }
>
> +/**
> + * tracecmd_local_events_system - create a tep from the
> + * events of the specified subsystem.
Keep the above on one line, even though it breaks the 80 character
limit.
-- Steve
> + *
> + * @tracing_dir: The directory that contains the events.
> + * @sys_name: Name of the subsystem, to load events from
> + *
> + * Returns a tep structure that contains the tep local to
> + * the system.
> + */
> +struct tep_handle *tracecmd_local_events_system(const char *tracing_dir,
> + char *sys_name)
> +{
> + struct tep_handle *tep = NULL;
> +
> + tep = tep_alloc();
> + if (!tep)
> + return NULL;
> +
> + if (tracecmd_fill_local_events_system(tracing_dir, tep, sys_name)) {
> + tep_free(tep);
> + tep = NULL;
> + }
> +
> + return tep;
> +}
>
next prev parent reply other threads:[~2019-01-21 9:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 19:18 [PATCH 0/7] trace-cmd [POC]: Timestamps sync using PTP-like algorithm, relying on vsock events Tzvetomir Stoyanov
2019-01-16 19:18 ` [PATCH 1/7] trace-cmd: Implemented new lib API: tracecmd_local_events_system() Tzvetomir Stoyanov
2019-01-21 9:02 ` Steven Rostedt [this message]
2019-01-16 19:18 ` [PATCH 2/7] trace-cmd: Added new option in trace.dat file for negative time offsets Tzvetomir Stoyanov
2019-01-21 9:08 ` Steven Rostedt
2019-01-22 13:28 ` Tzvetomir Stoyanov
2019-01-16 19:18 ` [PATCH 3/7] trace-cmd: Fixed logic in tracecmd_read_page_record() Tzvetomir Stoyanov
2019-01-21 9:09 ` Steven Rostedt
2019-01-22 13:36 ` Tzvetomir Stoyanov
2019-01-16 19:18 ` [PATCH 4/7] trace-cmd: Added implementation of htonll() and ntohll() Tzvetomir Stoyanov
2019-01-16 19:18 ` [PATCH 5/7] trace-cmd: Added user configured clock to the record context Tzvetomir Stoyanov
2019-01-21 9:19 ` Steven Rostedt
2019-01-22 13:43 ` Tzvetomir Stoyanov
2019-01-22 14:14 ` Slavomir Kaslev
2019-01-16 19:18 ` [PATCH 6/7] trace-cmd: Refactored make_instances() and tracecmd_remove_instances() Tzvetomir Stoyanov
2019-01-21 9:13 ` Steven Rostedt
2019-01-16 19:18 ` [PATCH 7/7] trace-cmd [POC]: Implemented timestamps synch PTP-like algorithm, using vsock events Tzvetomir Stoyanov
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=20190121040201.479f8ede@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.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).