qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-block@nongnu.org, Cleber Rosa <crosa@redhat.com>
Subject: [PULL 0/5] Tracing patches
Date: Mon,  4 Jan 2021 14:31:49 +0000	[thread overview]
Message-ID: <20210104143154.462212-1-stefanha@redhat.com> (raw)

The following changes since commit 41192db338588051f21501abc13743e62b0a5605:

  Merge remote-tracking branch 'remotes/ehabkost-gl/tags/machine-next-pull-request' into staging (2021-01-01 22:57:15 +0000)

are available in the Git repository at:

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

for you to fetch changes up to 7fb48c0ee1bbf5cc4c905e900b054096250e9f39:

  tracetool: show trace-events filename/lineno in fmt string errors (2021-01-04 14:24:58 +0000)

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

Show trace-events filename/lineno in fmt string errors and send -d trace:help
output to stdout for consistency.

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

Doug Evans (1):
  trace: Send "-d trace:help" output to stdout

Stefan Hajnoczi (4):
  tracetool: add output filename command-line argument
  tracetool: add out_lineno and out_next_lineno to out()
  tracetool: add input filename and line number to Event
  tracetool: show trace-events filename/lineno in fmt string errors

 docs/devel/tracing.txt              |  3 +-
 meson.build                         |  3 +-
 trace/control.h                     |  3 +-
 trace/control.c                     | 12 +++----
 scripts/tracetool.py                | 12 ++++---
 scripts/tracetool/__init__.py       | 53 +++++++++++++++++++++++++----
 scripts/tracetool/backend/ftrace.py |  4 +++
 scripts/tracetool/backend/log.py    |  4 +++
 scripts/tracetool/backend/syslog.py |  4 +++
 trace/meson.build                   | 21 ++++--------
 10 files changed, 83 insertions(+), 36 deletions(-)

-- 
2.29.2


             reply	other threads:[~2021-01-04 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 14:31 Stefan Hajnoczi [this message]
2021-01-04 14:31 ` [PULL 1/5] trace: Send "-d trace:help" output to stdout Stefan Hajnoczi
2021-01-04 15:12   ` Philippe Mathieu-Daudé
2021-01-04 14:31 ` [PULL 2/5] tracetool: add output filename command-line argument Stefan Hajnoczi
2021-01-04 14:31 ` [PULL 3/5] tracetool: add out_lineno and out_next_lineno to out() Stefan Hajnoczi
2021-01-04 14:31 ` [PULL 4/5] tracetool: add input filename and line number to Event Stefan Hajnoczi
2021-01-04 14:31 ` [PULL 5/5] tracetool: show trace-events filename/lineno in fmt string errors Stefan Hajnoczi
2021-01-04 14:42 ` [PULL 0/5] Tracing patches no-reply
2021-01-05 16:18 ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2020-01-30 21:38 Stefan Hajnoczi
2020-01-31 13:57 ` Peter Maydell
2020-01-31 14:38   ` Philippe Mathieu-Daudé
2020-01-31 14:45     ` Philippe Mathieu-Daudé
2020-01-31 15:25   ` Alex Bennée
2020-01-31 19:05 ` Peter Maydell

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=20210104143154.462212-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.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).