This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Systemtap + tracing processes inside a qemu guest
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "Richard W.M. Jones" <rjones at redhat dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Mon, 10 Oct 2011 09:35:30 -0400
- Subject: Re: Systemtap + tracing processes inside a qemu guest
- References: <20111010091026.GA15664@amd.home.annexia.org>
"Richard W.M. Jones" <rjones@redhat.com> writes:
> [...]
> However to get the complete picture I'd like to
> instrument the daemon too. The aim would be to get timing information
> across both the host program and the daemon:
>
> 0.001s program event #1 send message
> 0.005s daemon event #1 receive message
> 0.010s daemon event #2 send reply
> 0.025s program event #2 receive reply
> [...]
> What's possible at the moment?
You're looking for probing two separate systems (the host and the
guest) together. The general model does not stretch that far right
now (and probably would not be easy to extend it that way). The
closest thing would be running separate scripts, one on the host, and
one on the guest via --remote, and merging the events together after
the fact.
- FChE