From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: Matt Helsley <mhelsley@vmware.com>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH v7 5/9] trace-cmd: Refactored few functions in trace-record.c
Date: Thu, 21 Mar 2019 16:52:33 -0400 [thread overview]
Message-ID: <20190321165233.143ea97d@gandalf.local.home> (raw)
In-Reply-To: <CACqStoev5pRXxH64auUFkfwJ4sUG0hdQ6Uz8cQ9qphZJQK-qPw@mail.gmail.com>
On Thu, 21 Mar 2019 15:06:03 +0000
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> #!/bin/bash
>
> INST_NAME=vtest
> TRACE_INST_DIR=/sys/kernel/debug/tracing/instances
>
> mkdir $TRACE_INST_DIR/$INST_NAME
>
> echo "vmx_read_l1_tsc_offset" > $TRACE_INST_DIR/$INST_NAME/set_ftrace_filter
> echo "function" > $TRACE_INST_DIR/$INST_NAME/current_tracer
> echo "1" > $TRACE_INST_DIR/$INST_NAME/events/vsock/virtio_transport_recv_pkt/enable
> echo "len!=0" > $TRACE_INST_DIR/$INST_NAME/events/vsock/virtio_transport_recv_pkt/filter
> echo "mono_raw" > $TRACE_INST_DIR/$INST_NAME/trace_clock
> echo "1" > $TRACE_INST_DIR/$INST_NAME/tracing_on
>
> sleep 2
>
> echo "0" > $TRACE_INST_DIR/$INST_NAME/tracing_on
> echo "" > $TRACE_INST_DIR/$INST_NAME/set_ftrace_filter
> echo "nop" > $TRACE_INST_DIR/$INST_NAME/current_tracer
> echo "0" > $TRACE_INST_DIR/$INST_NAME/events/vsock/virtio_transport_recv_pkt/enable
> echo '0' > $TRACE_INST_DIR/$INST_NAME/events/vsock/virtio_transport_recv_pkt/filter
> echo "local" > $TRACE_INST_DIR/$INST_NAME/trace_clock
>
> rm -rf $TRACE_INST_DIR/$INST_NAME
Ah, that's because you are trying to remove the individual files. These
are not real files, and can not be removed. But you can remove the
directory.
rmdir $TRACE_INST_DIR/$INST_NAME
works as expected.
-- Steve
next prev parent reply other threads:[~2019-03-21 20:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 15:55 [PATCH v7 0/9] trace-cmd: Timetamps sync between host and guest machines, relying on vsock events Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 1/9] trace-cmd: Implemented new lib API: tracecmd_local_events_system() Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 2/9] trace-cmd: Added support for negative time offsets in trace.dat file Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 3/9] trace-cmd: Fix tracecmd_read_page_record() to read more than one event Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 4/9] trace-cmd: Added implementation of htonll() and ntohll() Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 5/9] trace-cmd: Refactored few functions in trace-record.c Tzvetomir Stoyanov
2019-03-19 18:21 ` Matt Helsley
2019-03-20 14:14 ` Tzvetomir Stoyanov
2019-03-20 14:35 ` Steven Rostedt
2019-03-21 15:06 ` Tzvetomir Stoyanov
2019-03-21 20:52 ` Steven Rostedt [this message]
2019-03-19 15:55 ` [PATCH v7 6/9] trace-cmd: Find and store pids of tasks, which run virtual CPUs of given VM Tzvetomir Stoyanov
2019-03-19 16:35 ` Slavomir Kaslev
2019-03-19 16:49 ` Steven Rostedt
2019-03-19 15:55 ` [PATCH v7 7/9] trace-cmd: Implemented new API tracecmd_add_option_v() Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 8/9] trace-cmd: Implemented new option in trace.dat file: TRACECMD_OPTION_TIME_SHIFT Tzvetomir Stoyanov
2019-03-19 17:58 ` Slavomir Kaslev
2019-03-19 18:00 ` Slavomir Kaslev
2019-03-20 14:39 ` Tzvetomir Stoyanov
2019-03-19 15:55 ` [PATCH v7 9/9] trace-cmd [POC]: Implemented timestamps synch algorithm, using vsock events Tzvetomir Stoyanov
2019-03-19 17:14 ` Slavomir Kaslev
2019-03-19 17:51 ` Steven Rostedt
2019-03-19 18:02 ` Slavomir Kaslev
2019-03-19 18:29 ` Matt Helsley
2019-03-19 18:40 ` Steven Rostedt
2019-03-20 15:06 ` Tzvetomir Stoyanov
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=20190321165233.143ea97d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhelsley@vmware.com \
--cc=tstoyanov@vmware.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;
as well as URLs for NNTP newsgroup(s).