From: Steven Rostedt <rostedt@goodmis.org>
To: Slavomir Kaslev <kaslevs@vmware.com>
Cc: Tzvetomir Stoyanov <tstoyanov@vmware.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v4 1/7] trace-cmd: Implemented new lib API: tracecmd_local_events_system()
Date: Fri, 22 Feb 2019 14:22:47 -0500 [thread overview]
Message-ID: <20190222142247.12e4b47c@gandalf.local.home> (raw)
In-Reply-To: <20190222155100.GA14440@box>
On Fri, 22 Feb 2019 17:51:04 +0200
Slavomir Kaslev <kaslevs@vmware.com> wrote:
> > @@ -1189,7 +1161,16 @@ int tracecmd_fill_local_events(const char *tracing_dir, struct tep_handle *peven
> > if (strcmp(name, ".") == 0 ||
> > strcmp(name, "..") == 0)
> > continue;
> > -
> > + if (sys_names) {
> > + i = 0;
> > + while (sys_names[i]) {
> > + if (strcmp(name, sys_names[i]) == 0)
> > + break;
> > + i++;
> > + }
> > + if (sys_names[i] == NULL)
> > + continue;
> > + }
>
> I think this would be better done in a separate function, say:
>
> static bool contains(const char *name, const char **names)
> {
> while (*names) {
> if (strcmp(name, *names++) == 0)
> return true;
> }
> return false;
> }
>
> and then simply have
>
> if (sys_names && !contains(name, sys_names))
> continue;
Actually, I would argue just to make it a for loop.
for (i = 0; sys_names[i]; i++) {
if (strcmp(name, sys_names[i]) == 0)
goto found;
}
continue;
found:
But if you really want the helper function, then have it check
sys_names too.
static bool contains(const char *name, const char * const * names)
{
if (!names)
return false;
for (; *names; names++)
if (strcmp(name, *names) == 0)
return true;
return false;
}
if (!contains(name, sys_names))
-- Steve
>
> here.
>
> > sys = append_file(events_dir, name);
> > ret = stat(sys, &st);
> > if (ret < 0 || !S_ISDIR(st.st_mode)) {
> > @@ -1217,6 +1198,58 @@ int tracecmd_fill_local_events(const char *tracing_dir, struct tep_handle *peven
> > return ret;
> > }
next prev parent reply other threads:[~2019-02-22 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 14:28 [PATCH v4 0/7][POC] trace-cmd: Timetamps sync between host and guest machines, relying on vsock events Tzvetomir Stoyanov
2019-02-22 14:28 ` [PATCH v4 1/7] trace-cmd: Implemented new lib API: tracecmd_local_events_system() Tzvetomir Stoyanov
2019-02-22 15:51 ` Slavomir Kaslev
2019-02-22 19:22 ` Steven Rostedt [this message]
2019-02-22 14:28 ` [PATCH v4 2/7] trace-cmd: Added support for negative time offsets in trace.dat file Tzvetomir Stoyanov
2019-02-22 14:28 ` [PATCH v4 3/7] trace-cmd: Fix tracecmd_read_page_record() to read more than one event Tzvetomir Stoyanov
2019-02-22 16:09 ` Slavomir Kaslev
2019-02-22 14:28 ` [PATCH v4 4/7] trace-cmd: Added implementation of htonll() and ntohll() Tzvetomir Stoyanov
2019-02-22 14:28 ` [PATCH v4 5/7] trace-cmd: Refactored make_instances() and tracecmd_remove_instances() Tzvetomir Stoyanov
2019-02-22 14:28 ` [PATCH v4 6/7] trace-cmd: Find and store pids of tasks, which run virtual CPUs of given VM Tzvetomir Stoyanov
2019-02-22 17:07 ` Slavomir Kaslev
2019-02-22 19:25 ` Steven Rostedt
2019-02-22 14:28 ` [PATCH v4 7/7] trace-cmd [POC]: Implemented timestamps synch 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=20190222142247.12e4b47c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kaslevs@vmware.com \
--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).