From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 0/6] Tracing patches
Date: Wed, 27 Jun 2018 13:58:41 +0100 [thread overview]
Message-ID: <20180627125847.5413-1-stefanha@redhat.com> (raw)
The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100)
are available in the Git repository at:
git://github.com/stefanha/qemu.git tags/tracing-pull-request
for you to fetch changes up to ec09f877532210e28e1d4b6b12896d3eb6d8e8d1:
trace: forbid floating point types (2018-06-27 11:09:29 +0100)
----------------------------------------------------------------
Pull request
* Trace TCG atomic memory accesses
* Document that trace event arguments cannot be floating point
----------------------------------------------------------------
Emilio G. Cota (5):
trace: fix misreporting of TCG access sizes for user-space
trace: simplify trace_mem functions
trace: expand mem_info:size_shift to 3 bits
trace: add trace_mem_build_info_no_se_be/le
trace: enable tracing of TCG atomics
Stefan Hajnoczi (1):
trace: forbid floating point types
docs/devel/tracing.txt | 5 ++
accel/tcg/atomic_template.h | 87 +++++++++++++++++++++--
include/exec/cpu_ldst_useronly_template.h | 11 ++-
trace/mem-internal.h | 58 ++++++++-------
trace/mem.h | 2 +-
migration/trace-events | 2 +-
qapi/trace-events | 2 +-
scripts/tracetool/__init__.py | 2 -
8 files changed, 130 insertions(+), 39 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-27 12:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 12:58 Stefan Hajnoczi [this message]
2018-06-27 12:58 ` [Qemu-devel] [PULL 1/6] trace: fix misreporting of TCG access sizes for user-space Stefan Hajnoczi
2018-06-27 12:58 ` [Qemu-devel] [PULL 2/6] trace: simplify trace_mem functions Stefan Hajnoczi
2018-06-27 12:58 ` [Qemu-devel] [PULL 3/6] trace: expand mem_info:size_shift to 3 bits Stefan Hajnoczi
2018-06-27 12:58 ` [Qemu-devel] [PULL 4/6] trace: add trace_mem_build_info_no_se_be/le Stefan Hajnoczi
2018-06-27 12:58 ` [Qemu-devel] [PULL 5/6] trace: enable tracing of TCG atomics Stefan Hajnoczi
2018-06-27 12:58 ` [Qemu-devel] [PULL 6/6] trace: forbid floating point types Stefan Hajnoczi
2018-06-28 13:26 ` [Qemu-devel] [PULL 0/6] Tracing patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 3:18 Stefan Hajnoczi
2019-01-31 12:52 ` 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=20180627125847.5413-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).