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>, Joe Jin <joe.jin@oracle.com>,
Srinivas Eeda <srinivas.eeda@oracle.com>,
Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Subject: [PATCH 0/5 v4]Kernel Access to Ftrace instances.
Date: Wed, 14 Aug 2019 10:55:22 -0700 [thread overview]
Message-ID: <1565805327-579-1-git-send-email-divya.indi@oracle.com> (raw)
In addition to patches introduced by commit f45d1225adb0 "tracing: Kernel
access to Ftrace instances") we also need the following patches to reliably
access ftrace instances from other kernel modules or components.
This version addresses the review comments/suggestions received for v3.
Please review the patches that follow.
Divya Indi (5):
tracing: Declare newly exported APIs in include/linux/trace.h
tracing: Verify if trace array exists before destroying it.
tracing: Adding NULL checks
tracing: Handle the trace array ref counter in new functions
tracing: New functions for kernel access to Ftrace instances
include/linux/trace.h | 10 +++++
include/linux/trace_events.h | 3 +-
kernel/trace/trace.c | 88 ++++++++++++++++++++++++++++++++++++++++++--
kernel/trace/trace.h | 4 +-
kernel/trace/trace_events.c | 25 ++++++++++++-
5 files changed, 121 insertions(+), 9 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-08-14 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 17:55 Divya Indi [this message]
2019-08-14 17:55 ` [PATCH 1/5] tracing: Declare newly exported APIs in include/linux/trace.h Divya Indi
2019-08-14 17:55 ` [PATCH 2/5] tracing: Verify if trace array exists before destroying it Divya Indi
2019-08-14 18:42 ` Aruna Ramakrishna
2019-08-14 17:55 ` [PATCH 3/5] tracing: Adding NULL checks Divya Indi
2019-08-14 17:55 ` [PATCH 4/5] tracing: Handle the trace array ref counter in new functions Divya Indi
2019-10-15 23:04 ` Steven Rostedt
2019-10-16 23:42 ` Divya Indi
2019-10-23 2:52 ` Steven Rostedt
2019-10-23 22:57 ` Divya Indi
2019-10-24 13:00 ` Steven Rostedt
2019-10-24 21:31 ` Divya Indi
2019-08-14 17:55 ` [PATCH 5/5] tracing: New functions for kernel access to Ftrace instances Divya Indi
2019-10-15 23:19 ` Steven Rostedt
2019-10-16 23:53 ` 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=1565805327-579-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=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
all inboxes | Powered by JetHome®