qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org, kraxel@redhat.com
Cc: stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/3] qxl trace events
Date: Wed, 14 Mar 2012 15:09:45 +0200	[thread overview]
Message-ID: <1331730588-19771-1-git-send-email-alevy@redhat.com> (raw)

Changes from v2:
 split 6+ trace points to X + X_rest (leave qid as first argument in both) (Stefan)
 (cleanup as requested by Gerd)
 no trace event for pipe write failure, left dprint there anyway.
 indentation in a separate patch
 qxl-render.c: qxl_render prefix
 spice-display.c: qemu_spice functions trace names prefixed with qemu_spice

Changes from v1:
 add qid prefix to all tracepoints (except vga update which makes no sense)
 rename to ring where suggested (Gerd)
 add some trace points to spice-display
 drop enter/exit in favor of a single command (Gerd)
 some sorting of the trace event list

Alon Levy (3):
  qxl: switch qxl.c to trace-events
  qxl/qxl_render.c: add trace events
  qxl: init_pipe_signaling: exit on failure

 hw/qxl-render.c    |   13 ++---
 hw/qxl.c           |  160 ++++++++++++++++++++++++++--------------------------
 trace-events       |   69 ++++++++++++++++++++++
 ui/spice-display.c |   13 ++++-
 4 files changed, 163 insertions(+), 92 deletions(-)

-- 
1.7.9.3

             reply	other threads:[~2012-03-14 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 13:09 Alon Levy [this message]
2012-03-14 13:09 ` [Qemu-devel] [PATCH v3 1/3] qxl: switch qxl.c to trace-events Alon Levy
2012-03-14 13:09 ` [Qemu-devel] [PATCH v3 2/3] qxl/qxl_render.c: add trace events Alon Levy
2012-03-14 13:09 ` [Qemu-devel] [PATCH v3 3/3] qxl: init_pipe_signaling: exit on failure Alon Levy
2012-03-15 11:10 ` [Qemu-devel] [PATCH v3 0/3] qxl trace events 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=1331730588-19771-1-git-send-email-alevy@redhat.com \
    --to=alevy@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).