linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Divya Indi <divya.indi@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Kernel access to ftrace instances
Date: Tue, 19 Mar 2019 16:16:55 -0400	[thread overview]
Message-ID: <20190319161655.2824746c@gandalf.local.home> (raw)
In-Reply-To: <1552692925-17240-2-git-send-email-divya.indi@oracle.com>

On Fri, 15 Mar 2019 16:35:25 -0700
Divya Indi <divya.indi@oracle.com> wrote:

> Ftrace provides the feature “instances” that provides the capability to
> create multiple Ftrace ring buffers. However, currently these buffers
> are created/accessed via userspace only. The kernel APIs providing these
> features are not exported, hence cannot be used by other kernel
> components.
> 
> This patch aims to extend this infrastructure to provide the
> flexibility to create/log/remove/ enable-disable existing trace events
> to these buffers from within the kernel.
> 
>

Thanks for sending this. I'm currently working on some other changes,
but will look in this when I'm finished with the other work. Should be
within this week.

-- Steve

  reply	other threads:[~2019-03-19 20:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 23:35 [RFC] Kernel access to Ftrace instances Divya Indi
2019-03-15 23:35 ` [PATCH] tracing: Kernel access to ftrace instances Divya Indi
2019-03-19 20:16   ` Steven Rostedt [this message]
2019-03-20 18:20     ` divya.indi
2019-03-20 18:28 [RFC] Kernel access to Ftrace instances Divya Indi
2019-03-20 18:28 ` [PATCH] tracing: " Divya Indi
2019-03-27 16:29   ` Steven Rostedt
2019-05-16  0:09   ` Masami Hiramatsu
2019-05-16  1:51     ` Divya Indi
2019-05-16  3:05       ` Masami Hiramatsu
2019-05-16  3:24         ` Steven Rostedt
2019-05-20 15:23           ` Steven Rostedt
2019-05-20 15:29             ` 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=20190319161655.2824746c@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=divya.indi@oracle.com \
    --cc=linux-kernel@vger.kernel.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).