From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Maneesh Soni <maneesh@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Tracing: outstanding tasks
Date: Fri, 2 Jul 2010 09:53:14 +0530 [thread overview]
Message-ID: <20100702042314.GA32121@in.ibm.com> (raw)
In-Reply-To: <AANLkTinLTifNIALGVbzKVFUq2F4xlo_WcnQiGbPFxGjt@mail.gmail.com>
On Wed, Jun 30, 2010 at 12:51:59PM +0100, Stefan Hajnoczi wrote:
> On Wed, Jun 30, 2010 at 11:20 AM, Prerna Saxena
> <prerna@linux.vnet.ibm.com> wrote:
> > On 06/26/2010 01:36 PM, Stefan Hajnoczi wrote:
> >>
> >> 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.
...
> >> 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.
Another feature needed would be a facility to trigger a sync of trace buffer to
file even if the buffer isn't full.
Ananth
next prev parent reply other threads:[~2010-07-02 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 8:06 [Qemu-devel] Tracing: outstanding tasks Stefan Hajnoczi
2010-06-30 10:20 ` Prerna Saxena
2010-06-30 11:51 ` Stefan Hajnoczi
2010-07-02 4:23 ` Ananth N Mavinakayanahalli [this message]
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=20100702042314.GA32121@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=maneesh@linux.vnet.ibm.com \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.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).