From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: saxena.prerna@in.ibm.com
Subject: [Qemu-devel] Tracing: outstanding tasks
Date: Sat, 26 Jun 2010 09:06:59 +0100 [thread overview]
Message-ID: <20100626080657.GA4806@stefan-thinkpad.transitives.com> (raw)
Here are the outstanding tasks for QEMU tracing, which Prerna and I have
been working on. Tracing aids debugging, profiling, and observing
execution via lightweight logging at key points in the code path.
The current prototype is available from the 'tracing' branch at:
http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/tracing
This email is both to help Prerna and me focus our efforts, as well as a
roadmap for the QEMU community to discuss and comment on.
Here are the outstanding tasks for a tracing patchset that can be
proposed for merge:
1. Integration with QMP
Owner: Prerna
Currently the trace commands are available from the monitor but a QMP interface
is needed.
2. More tracepoints need to be added for instrumenting other qemu components
such as virtio drivers, etc.
Owner: ?
QEMU must come with a useful set of trace events that allows people to get up
and running quickly. Focus areas include:
* guest device emulation
* host devices
* lifecycle and runloop
* memory management
* live migration
3. Documentation
Owner: Stefan
User documentation that explains how to collect traces and add new trace
events. I have committed documentation to the tracing branch here:
http://repo.or.cz/w/qemu/stefanha.git/blob_plain/91fde34dc6bfe01af6d5e9265f6a81535d6add15:/docs/tracing.txt
4. Fix i386-linux-user build
Owner: Prerna
LINK i386-linux-user/qemu-i386
../simpletrace.o: In function `do_info_all_trace_events':
/home/stefanha/qemu/simpletrace.c:88: undefined reference to `monitor_printf'
../simpletrace.o: In function `do_info_trace':
/home/stefanha/qemu/simpletrace.c:77: undefined reference to `monitor_printf'
5. Out-of-line trace file write-out
Owner: Stefan
Trace buffers are written out to file synchronously. The vcpu thread should
not be blocked so an async write-out mechanism is needed.
6. Trace file command
Owner: ?
Traces are written out to hardcoded /tmp/trace.log. This must be configurable.
Tracing at startup time should still be possible so configuration needs to
happen early.
7. Binary trace format finalization
Owner: Stefan
We should leave room for extension. I suggest partitioning the Event ID
namespace into normal events and special events. The __trace_begin special
event is defined to contain the file format version and/or trace record size in
bytes as the first trace record in the file.
This way, post-processing tools can check the format of the binary trace file.
8. QMP/monitor command review
Owner: Prerna, Stefan
Are we happy to support the trace commands in the longer term (i.e. did we get
the commands and syntax right)? Is input being validated properly?
Stefan
next reply other threads:[~2010-06-26 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 8:06 Stefan Hajnoczi [this message]
2010-06-30 10:20 ` [Qemu-devel] Tracing: outstanding tasks Prerna Saxena
2010-06-30 11:51 ` Stefan Hajnoczi
2010-07-02 4:23 ` Ananth N Mavinakayanahalli
2010-07-02 10:13 ` Stefan Hajnoczi
2010-07-06 14:26 ` Stefan Hajnoczi
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=20100626080657.GA4806@stefan-thinkpad.transitives.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=saxena.prerna@in.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;
as well as URLs for NNTP newsgroup(s).