linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, David Ahern <dsahern@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REQ]: 'perf probe --del *:*' should remove both uprobes and kprobes
Date: Tue, 31 Mar 2015 17:33:43 +0900	[thread overview]
Message-ID: <551A5BE7.4020502@hitachi.com> (raw)
In-Reply-To: <20150330201248.GA9116@kernel.org>

(2015/03/31 5:12), Arnaldo Carvalho de Melo wrote:
> How it is now:
> 
> [root@ssdandy acme]# perf probe --del *:*
> Removed event: probe:icmp_rcv
> [root@ssdandy acme]# perf probe --del *:*
> Removed event: probe_ex:main
> [root@ssdandy acme]# perf probe --del *:*
> Info: Event "*:*" does not exist.
>   Error: Failed to delete events.
> [root@ssdandy
> 
> I.e. it'll first remove all kprobes, then bail out, next time we ask for
> everything to be deleted, there are no kprobes, so it will try the
> uprobes, removing it all, I think it should not be a two step process
> :-)

Yes, this should clear all events if user gives "*:*".

Thank you for reporting! :)

> 
> - Arnaldo
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



      reply	other threads:[~2015-03-31  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 20:12 [REQ]: 'perf probe --del *:*' should remove both uprobes and kprobes Arnaldo Carvalho de Melo
2015-03-31  8:33 ` Masami Hiramatsu [this message]

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=551A5BE7.4020502@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@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).