qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PULL 0/6] Tracing patches
Date: Wed, 30 Jan 2019 11:18:11 +0800	[thread overview]
Message-ID: <20190130031817.27780-1-stefanha@redhat.com> (raw)

The following changes since commit f6b06fcceef465de0cf2514c9f76fe0192896781:

  Merge remote-tracking branch 'remotes/kraxel/tags/ui-20190121-pull-request' into staging (2019-01-23 17:57:47 +0000)

are available in the Git repository at:

  git://github.com/stefanha/qemu.git tags/tracing-pull-request

for you to fetch changes up to 57b7bdf426445d8356171135308dfe6d7d5fb612:

  trace: rerun tracetool after ./configure changes (2019-01-30 10:57:03 +0800)

----------------------------------------------------------------
Pull request

User-visible changes:
 * The new qemu-trace-stap script makes it convenient to collect traces without
   writing SystemTap scripts.  See "man qemu-trace-stap" for details.

----------------------------------------------------------------

Daniel P. Berrangé (4):
  display: ensure qxl log_buf is a nul terminated string
  trace: enforce that every trace-events file has a final newline
  trace: forbid use of %m in trace event format strings
  trace: add ability to do simple printf logging via systemtap

Stefan Hajnoczi (1):
  trace: rerun tracetool after ./configure changes

Vladimir Sementsov-Ogievskiy (1):
  trace: improve runstate tracing

 MAINTAINERS                          |   1 +
 docs/devel/tracing.txt               |   4 +
 Makefile                             |  26 ++--
 Makefile.target                      |  11 +-
 hw/display/qxl.c                     |  14 ++-
 hw/vfio/pci.c                        |   2 +-
 vl.c                                 |   7 +-
 hw/display/trace-events              |   2 +-
 hw/gpio/trace-events                 |   2 +-
 hw/vfio/trace-events                 |   2 +-
 scripts/qemu-trace-stap              | 175 +++++++++++++++++++++++++++
 scripts/qemu-trace-stap.texi         | 140 +++++++++++++++++++++
 scripts/tracetool/__init__.py        |   6 +
 scripts/tracetool/format/log_stap.py | 127 +++++++++++++++++++
 trace-events                         |   4 +-
 15 files changed, 502 insertions(+), 21 deletions(-)
 create mode 100755 scripts/qemu-trace-stap
 create mode 100644 scripts/qemu-trace-stap.texi
 create mode 100644 scripts/tracetool/format/log_stap.py

-- 
2.20.1

             reply	other threads:[~2019-01-30  3:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  3:18 Stefan Hajnoczi [this message]
2019-01-30  3:18 ` [Qemu-devel] [PULL 1/6] display: ensure qxl log_buf is a nul terminated string Stefan Hajnoczi
2019-01-30  3:18 ` [Qemu-devel] [PULL 2/6] trace: enforce that every trace-events file has a final newline Stefan Hajnoczi
2019-01-30  3:18 ` [Qemu-devel] [PULL 3/6] trace: forbid use of %m in trace event format strings Stefan Hajnoczi
2019-01-30  3:18 ` [Qemu-devel] [PULL 4/6] trace: add ability to do simple printf logging via systemtap Stefan Hajnoczi
2019-01-30  3:18 ` [Qemu-devel] [PULL 5/6] trace: improve runstate tracing Stefan Hajnoczi
2019-01-30  3:18 ` [Qemu-devel] [PULL 6/6] trace: rerun tracetool after ./configure changes Stefan Hajnoczi
2019-01-31 12:52 ` [Qemu-devel] [PULL 0/6] Tracing patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 12:58 Stefan Hajnoczi
2018-06-28 13:26 ` Peter Maydell
2014-02-19 15:45 Stefan Hajnoczi
2014-02-19 16:01 ` Lluís Vilanova
2014-02-20 10:24   ` Stefan Hajnoczi
2014-02-21 14:46 ` Peter Maydell
2011-04-26 12:25 Stefan Hajnoczi
2011-04-26 13:19 ` Anthony Liguori

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=20190130031817.27780-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).