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 v2 8/8] trace-cmd: Add new function to set log level
Date: Fri, 14 May 2021 05:53:03 +0300 [thread overview]
Message-ID: <CAPpZLN5v_oTqaVWyXmHK5s0xtLxtMAbDuqtedy72gxroS2tPFQ@mail.gmail.com> (raw)
In-Reply-To: <20210513173605.030af4cd@gandalf.local.home>
On Fri, May 14, 2021 at 12:36 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 7 May 2021 12:53:33 +0300
> "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
>
> > Introduce a new trace-cmd internal function to set the application log
> > level.
> > trace_set_verbose()
> > The log level can be set using string with log id or log name.
> >
> > Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> > ---
> > tracecmd/include/trace-local.h | 2 ++
> > tracecmd/trace-cmd.c | 41 ++++++++++++++++++++++++++++++++++
> > 2 files changed, 43 insertions(+)
> >
> > diff --git a/tracecmd/include/trace-local.h b/tracecmd/include/trace-local.h
> > index b3997d00..8da07c83 100644
> > --- a/tracecmd/include/trace-local.h
> > +++ b/tracecmd/include/trace-local.h
> > @@ -39,6 +39,8 @@ void usage(char **argv);
> > extern int silence_warnings;
> > extern int show_status;
> >
> > +int trace_set_verbose(char *level);
> > +
> > struct pid_record_data {
> > int pid;
> > int brass[2];
> > diff --git a/tracecmd/trace-cmd.c b/tracecmd/trace-cmd.c
> > index 60cd3ea1..4e4a73af 100644
> > --- a/tracecmd/trace-cmd.c
> > +++ b/tracecmd/trace-cmd.c
> > @@ -45,6 +45,47 @@ void *malloc_or_die(unsigned int size)
> > return data;
> > }
> >
> > +static struct trace_log_severity {
> > + int id;
> > + const char *name;
> > +} log_severtity[] = {
>
> Is there a reason for the extra 't' in severity?
It's a typo.
>
> > + { .id = TEP_LOG_NONE, .name = "none" },
> > + { .id = TEP_LOG_CRITICAL, .name = "crit" },
> > + { .id = TEP_LOG_ERROR, .name = "err" },
> > + { .id = TEP_LOG_WARNING, .name = "warn" },
> > + { .id = TEP_LOG_INFO, .name = "info" },
> > + { .id = TEP_LOG_DEBUG, .name = "debug" },
> > + { .id = TEP_LOG_ALL, .name = "all" },
> > +};
> > +
> > +int trace_set_verbose(char *level)
> > +{
> > + int id;
> > +
> > + if (!level)
> > + return -1;
> > +
> > + if (isdigit(level[0])) {
> > + id = atoi(level);
> > + if (id >= TEP_LOG_NONE && id <= TEP_LOG_ALL) {
> > + tracecmd_set_loglevel(id);
> > + return 0;
> > + }
> > + } else {
> > + int size = sizeof(log_severtity) / sizeof(log_severtity[0]);
>
> This can be shortened to:
>
> int size = ARRAY_SIZE(log_severity);
>
> Or at least we need to copy that macro to something that trace-cmd core has
> access to (see lib/trace-cmd/include/private/trace-cmd-private.h)
>
>
> > + int i;
> > +
> > + for (i = 0; i < size; i++) {
> > + if (strlen(level) >= strlen(log_severtity[i].name) &&
>
> Why the strlen test? It's OK to pass in "debugignorme"? What's the use case
> for this?
>
> Anyway, I applied the first two patches of this series.
>
> -- Steve
>
>
> > + !strncmp(level, log_severtity[i].name, strlen(log_severtity[i].name))) {
> > + tracecmd_set_loglevel(log_severtity[i].id);
> > + return 0;
> > + }
> > + }
> > + }
> > +
> > + return -1;
> > +}
> >
> > /**
> > * struct command
>
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center
prev parent reply other threads:[~2021-05-14 2:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:53 [PATCH v2 0/8] Changes to trace-cmd logs Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 1/8] trace-cmd library: Use tep_vprint() for logs Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 2/8] trace-cmd library: Add tracecmd_info() log function Tzvetomir Stoyanov (VMware)
2021-05-13 21:22 ` Steven Rostedt
2021-05-07 9:53 ` [PATCH v2 3/8] trace-cmd library: Add log levels Tzvetomir Stoyanov (VMware)
2021-05-13 21:23 ` Steven Rostedt
2021-05-14 2:51 ` Tzvetomir Stoyanov
2021-05-14 3:19 ` Steven Rostedt
2021-05-07 9:53 ` [PATCH v2 4/8] trace-cmd library: Document the API for " Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 5/8] trace-cmd library: Renamed tracecmd_fatal() to tracecmd_critical() Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 6/8] trace-cmd library: Set debug log level in debug mode Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 7/8] trace-cmd report: Set the log level with -V and -q options Tzvetomir Stoyanov (VMware)
2021-05-07 9:53 ` [PATCH v2 8/8] trace-cmd: Add new function to set log level Tzvetomir Stoyanov (VMware)
2021-05-13 21:36 ` Steven Rostedt
2021-05-14 2:53 ` Tzvetomir Stoyanov [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=CAPpZLN5v_oTqaVWyXmHK5s0xtLxtMAbDuqtedy72gxroS2tPFQ@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).