From: Steven Rostedt <rostedt@goodmis.org>
To: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
Cc: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-kernel@vger.kernel.org, yrl.pp-manager.tt@hitachi.com
Subject: Re: [PATCH V2 0/5] trace-cmd: Support the feature recording trace data of guests on the host
Date: Mon, 14 Oct 2013 17:26:37 -0400 [thread overview]
Message-ID: <20131014172637.2ced6be9@gandalf.local.home> (raw)
In-Reply-To: <20130913020627.28927.69090.stgit@yunodevel>
On Fri, 13 Sep 2013 11:06:27 +0900
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com> wrote:
> <How to use>
> 1. Run virt-server on a host
> # trace-cmd virt-server
>
> 2. Make guest domain directory
> # mkdir -p /tmp/trace-cmd/virt/<domain>
> # chmod 710 /tmp/trace-cmd/virt/<domain>
> # chgrp qemu /tmp/trace-cmd/virt/<domain>
Quick comment. I think the above should be done by trace-cmd. At least
have options for it like:
trace-cmd virt-server -d /tmp/trace-cmd/virt/domain -m 710 -g qemu
Perhaps default some of those, and have trace-cmd print out:
Process Directory: /tmp/trace-cmd/virt/domain
Directory permission: 0710
Group: qemu
OK, now to look at the actual code ;-)
-- Steve
>
> 3. Make FIFO on the host
> # mkfifo /tmp/trace-cmd/virt/<domain>/trace-path-cpu{0,1,...,X}.{in,out}
>
> 4. Set up of virtio-serial pipe of a guest on the host
> Add the following tags to domain XML files.
> # virsh edit <domain>
> <channel type='unix'>
> <source mode='connect' path='/tmp/trace-cmd/virt/agent-ctl-path'/>
> <target type='virtio' name='agent-ctl-path'/>
> </channel>
> <channel type='pipe'>
> <source path='/tmp/trace-cmd/virt/<domain>/trace-path-cpu0'/>
> <target type='virtio' name='trace-path-cpu0'/>
> </channel>
> ... (cpu1, cpu2, ...)
>
> 5. Boot the guest
> # virsh start <domain>
>
> 6. Execute "record --virt" on the guest
> # trace-cmd record --virt -e sched*
>
next prev parent reply other threads:[~2013-10-14 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 2:06 Yoshihiro YUNOMAE
2013-09-13 2:06 ` [PATCH V2 1/5] [CLEANUP] trace-cmd: Split out binding a port and fork reader from open_udp() Yoshihiro YUNOMAE
2013-09-13 2:06 ` [PATCH V2 2/5] trace-cmd: Apply the trace-msg protocol for communication between a server and clients Yoshihiro YUNOMAE
2013-10-15 2:21 ` Steven Rostedt
2013-10-17 6:34 ` Yoshihiro YUNOMAE
2013-10-17 21:21 ` Steven Rostedt
2013-10-18 2:19 ` Steven Rostedt
2013-10-22 8:53 ` Yoshihiro YUNOMAE
2013-09-13 2:06 ` [PATCH V2 3/5] trace-cmd: Use poll(2) to wait for a message Yoshihiro YUNOMAE
2013-09-13 2:06 ` [PATCH V2 4/5] trace-cmd: Add virt-server mode for a virtualization environment Yoshihiro YUNOMAE
2013-10-18 2:32 ` Steven Rostedt
2013-10-22 8:55 ` Yoshihiro YUNOMAE
2013-09-13 2:06 ` [PATCH V2 5/5] trace-cmd: Add --virt option for record mode Yoshihiro YUNOMAE
2013-10-11 1:39 ` [PATCH V2 0/5] trace-cmd: Support the feature recording trace data of guests on the host Yoshihiro YUNOMAE
2013-10-11 1:46 ` Steven Rostedt
2013-10-14 21:26 ` Steven Rostedt [this message]
2013-10-17 6:32 ` Yoshihiro YUNOMAE
2013-10-17 21:11 ` Steven Rostedt
2013-10-18 15:06 ` Steven Rostedt
2013-10-22 8:53 ` Yoshihiro YUNOMAE
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=20131014172637.2ced6be9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=yoshihiro.yunomae.ez@hitachi.com \
--cc=yrl.pp-manager.tt@hitachi.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
all inboxes | Powered by JetHome®