qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fabien Chouteau <chouteau@adacore.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] New trace-event backend: stdio
Date: Wed, 26 Jan 2011 09:50:30 +0000	[thread overview]
Message-ID: <AANLkTimM7EbYB8Du1JPx7swvUfAcnf8Pj3GbuEKD6Oav@mail.gmail.com> (raw)
In-Reply-To: <e7c3ac0f4cbd0d0c1dd1d213cd2c871393bf1846.1295890311.git.chouteau@adacore.com>

On Mon, Jan 24, 2011 at 5:33 PM, Fabien Chouteau <chouteau@adacore.com> wrote:
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index 963c504..de033ad 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.txt
> @@ -133,6 +133,11 @@ source tree.  It may not be as powerful as platform-specific or third-party
>  trace backends but it is portable.  This is the recommended trace backend
>  unless you have specific needs for more advanced backends.
>
> +=== Stdio ===
> +
> +The "stdio" backend sends trace events directly to standard output during
> +emulation.
> +

This is a reasonable backend for development/debugging.  It's just a
small step from DPRINTF() and that might work well with people's
existing development workflows.

Since most other QEMU diagnostics go to stderr, please use it here
too.  Also please change the name to "stderr" so it is immediately
obvious what this backend does.

> @@ -236,6 +237,55 @@ linetoc_end_simple()
>  EOF
>  }
>
> +#STDIO
> +linetoh_begin_stdio()
> +{
> +    return
> +}
> +
> +linetoh_stdio()
> +{
> +    local name args argnamess argc fmt

local name args argnames argc state fmt

Stefan

  parent reply	other threads:[~2011-01-26  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 17:33 [Qemu-devel] [PATCH][RFC] New trace-event backend: stdio Fabien Chouteau
2011-01-26  8:59 ` Fabien Chouteau
2011-01-26  9:50 ` Stefan Hajnoczi [this message]
2011-01-26 10:18 ` 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=AANLkTimM7EbYB8Du1JPx7swvUfAcnf8Pj3GbuEKD6Oav@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=chouteau@adacore.com \
    --cc=qemu-devel@nongnu.org \
    /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).