From: Steven Rostedt <rostedt@goodmis.org>
To: Divya Indi <divya.indi@oracle.com>
Cc: linux-kernel@vger.kernel.org,
Srinivas Eeda <srinivas.eeda@oracle.com>,
Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Subject: Re: [PATCH 1/3] tracing: Relevant changes for kernel access to Ftrace instances.
Date: Mon, 17 Jun 2019 19:34:14 -0400 [thread overview]
Message-ID: <20190617193414.6bc6d5e4@gandalf.local.home> (raw)
In-Reply-To: <1560357259-3497-2-git-send-email-divya.indi@oracle.com>
On Wed, 12 Jun 2019 09:34:17 -0700
Divya Indi <divya.indi@oracle.com> wrote:
Hi Divya,
First, make sure the patches are all replied to the cover patch [0/3].
That is, patch 1, 2 and 3 should all be in reply to [0/3] to see a all
the patches at the same level, and that makes replies easy to stand out.
Having patch 2 a reply to patch 1 and patch 3 a reply to patch 2, makes
it hard to see what comments are for what patches.
> For commit f45d1225adb0 ("tracing: Kernel access to Ftrace instances")
> Adding the following changes to ensure other kernel components can
> use these functions -
> 1) Remove static keyword for newly exported fn - ftrace_set_clr_event.
> 2) Add the req functions to header file include/linux/trace_events.h.
The above change log is hard to parse. The "Adding" looks to be a start
of a new sentence, and what changes and what components can use these
functions?
Also avoid shorten words ("fn", "req") that just makes trying to figure
out what is being said that more confusing.
>
> Signed-off-by: Divya Indi <divya.indi@oracle.com>
> ---
> include/linux/trace_events.h | 6 ++++++
> kernel/trace/trace_events.c | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/trace_events.h b/include/linux/trace_events.h
> index 8a62731..d7b7d85 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -539,6 +539,12 @@ extern int trace_define_field(struct trace_event_call *call, const char *type,
>
> #define is_signed_type(type) (((type)(-1)) < (type)1)
>
> +void trace_printk_init_buffers(void);
> +int trace_array_printk(struct trace_array *tr, unsigned long ip,
> + const char *fmt, ...);
> +struct trace_array *trace_array_create(const char *name);
> +int trace_array_destroy(struct trace_array *tr);
> +int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set);
These function are declared elsewhere. If we are adding them here, then
they should be removed from the other places.
But trace_events.h is not the proper place to put these. The
trace_events.h file is only for code used in the TRACE_EVENT() macros.
The proper file is include/linux/trace.h
-- Steve
> int trace_set_clr_event(const char *system, const char *event, int set);
>
> /*
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 0ce3db6..b6b4618 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -795,7 +795,7 @@ static int __ftrace_set_clr_event(struct trace_array *tr, const char *match,
> return ret;
> }
>
> -static int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
> +int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
> {
> char *event = NULL, *sub = NULL, *match;
> int ret;
next prev parent reply other threads:[~2019-06-17 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:34 [RFC][v2] Kernel Access to Ftrace Instances Divya Indi
2019-06-12 16:34 ` [PATCH 1/3] tracing: Relevant changes for kernel access to Ftrace instances Divya Indi
2019-06-12 16:34 ` [PATCH 2/3] tracing: Adding additional NULL checks Divya Indi
2019-06-12 16:34 ` [PATCH 3/3] tracing: Add 2 new funcs. for kernel access to Ftrace instances Divya Indi
2019-06-17 23:45 ` Steven Rostedt
2019-06-19 14:23 ` Divya Indi
2019-06-17 23:36 ` [PATCH 2/3] tracing: Adding additional NULL checks Steven Rostedt
2019-06-17 23:34 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-05 0:42 [RFC] Kernel Access to Ftrace instances Divya Indi
2019-06-05 0:42 ` [PATCH 1/3] tracing: Relevant changes for kernel access " Divya Indi
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=20190617193414.6bc6d5e4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aruna.ramakrishna@oracle.com \
--cc=divya.indi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.eeda@oracle.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
all inboxes | Powered by JetHome®