Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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
Message-Id: <1573679762-7774-1-git-send-email-divya.indi@oracle.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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