From: Divya Indi <divya.indi@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: Divya Indi <divya.indi@oracle.com>,
Aruna Ramakrishna <aruna.ramakrishna@oracle.com>,
Srinivas Eeda <srinivas.eeda@oracle.com>,
Joe Jin <joe.jin@oracle.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>
Subject: [RFC v4] Kernel access to ftrace instances.
Date: Wed, 13 Nov 2019 13:15:57 -0800 [thread overview]
Message-ID: <1573679762-7774-1-git-send-email-divya.indi@oracle.com> (raw)
Hi,
Please review the patches that follow -
[PATCH 1/5] tracing: Declare newly exported APIs in include/linux/trace.h
[PATCH 2/5] tracing: Verify if trace array exists before destroying it.
[PATCH 3/5] tracing: Adding NULL checks
[PATCH 4/5] tracing: Adding new functions for kernel access to Ftrace instances.
[PATCH 5/5] tracing: Sample module to demonstrate kernel access to Ftrace instances.
This patchset addresses the feedback recieved for v3.
Changes from v3 include -
1) trace_array_get_by_name() replaces trace_array_lookup and
with its new implementation we no longer need to export
trace_array_create().
If a trace array with given name exists, this func returns a pointer
to this trace array (Previously, trace_array_lookup()).
If does not exist, create a new trace array (Previously done by trace_array_create()).
2) A new trace array will always have ref ctr = 1 on creation.
Destroying a trace array will require its ref ctr to be 1.
3) trace_array_set_clr_event(): Uses boolean instead of 0/1 to enable/disable
events to a trace array.
4) Sample module reflects the above changes. It is now part of the same patch-set.
Thanks,
Divya
next reply other threads:[~2019-11-13 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 21:15 Divya Indi [this message]
2019-11-13 21:15 ` [PATCH 1/5] tracing: Declare newly exported APIs in include/linux/trace.h Divya Indi
2019-11-13 21:15 ` [PATCH 2/5] tracing: Verify if trace array exists before destroying it Divya Indi
2019-11-13 21:16 ` [PATCH 3/5] tracing: Adding NULL checks Divya Indi
2019-11-13 21:16 ` [PATCH 4/5] tracing: Adding new functions for kernel access to Ftrace instances Divya Indi
2019-11-13 21:16 ` [PATCH 5/5] tracing: Sample module to demonstrate " Divya Indi
2019-11-14 17:17 ` [PATCH 4/5] tracing: Adding new functions for " Steven Rostedt
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=1573679762-7774-1-git-send-email-divya.indi@oracle.com \
--to=divya.indi@oracle.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=rostedt@goodmis.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
Powered by JetHome