public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL PATCH 1/2] doc: trace/kprobes: add information about NOKPROBE_SYMBOL
Date: Thu, 9 Mar 2017 08:57:11 +0100	[thread overview]
Message-ID: <20170309085711.84392f1690725687a3a7c0f9@kernel.org> (raw)
In-Reply-To: <d924e20de099579ace4286e610304f054cd798db.1488991670.git.naveen.n.rao@linux.vnet.ibm.com>

On Wed,  8 Mar 2017 22:34:14 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:

> Update kprobe tracer documentation to also mention that
> NOKPROBE_SYMBOL() and nokprobe_inline add symbols to the kprobes
> blacklist.

Thanks for update!

Acked-by: Masami Hiramatsu <mhiramat@kernel.org>

> 
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
> ---
>  Documentation/trace/kprobetrace.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/trace/kprobetrace.txt b/Documentation/trace/kprobetrace.txt
> index 41ef9d8efe95..5ea85059db3b 100644
> --- a/Documentation/trace/kprobetrace.txt
> +++ b/Documentation/trace/kprobetrace.txt
> @@ -8,8 +8,9 @@ Overview
>  --------
>  These events are similar to tracepoint based events. Instead of Tracepoint,
>  this is based on kprobes (kprobe and kretprobe). So it can probe wherever
> -kprobes can probe (this means, all functions body except for __kprobes
> -functions). Unlike the Tracepoint based event, this can be added and removed
> +kprobes can probe (this means, all functions except those with
> +__kprobes/nokprobe_inline annotation and those marked NOKPROBE_SYMBOL).
> +Unlike the Tracepoint based event, this can be added and removed
>  dynamically, on the fly.
>  
>  To enable this feature, build your kernel with CONFIG_KPROBE_EVENTS=y.
> -- 
> 2.11.1
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2017-03-09  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 17:04 [TRIVIAL PATCH 0/2] kprobes: a couple of trivial changes Naveen N. Rao
2017-03-08 17:04 ` [TRIVIAL PATCH 1/2] doc: trace/kprobes: add information about NOKPROBE_SYMBOL Naveen N. Rao
2017-03-09  7:57   ` Masami Hiramatsu [this message]
2017-03-15 18:44   ` [tip:perf/core] " tip-bot for Naveen N. Rao
2017-03-08 17:04 ` [TRIVIAL PATCH 2/2] kprobes: Convert kprobe_exceptions_notify to use NOKPROBE_SYMBOL Naveen N. Rao
2017-03-09  7:56   ` Masami Hiramatsu
2017-03-15 18:44   ` [tip:perf/core] " tip-bot for Naveen N. Rao

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=20170309085711.84392f1690725687a3a7c0f9@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=naveen.n.rao@linux.vnet.ibm.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