From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 0/8] Tracing patches
Date: Tue, 28 Jun 2016 22:27:22 +0100 [thread overview]
Message-ID: <1467149250-31165-1-git-send-email-stefanha@redhat.com> (raw)
The following changes since commit d7f30403576f04f1f3a5fb5a1d18cba8dfa7a6d2:
cputlb: don't cpu_abort() if guest tries to execute outside RAM or RAM (2016-06-28 18:50:53 +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 9c15e70086f3343bd810c6150d92ebfd6f346fcf:
trace: [*-user] Add events to trace guest syscalls in syscall emulation mode (2016-06-28 21:14:12 +0100)
----------------------------------------------------------------
----------------------------------------------------------------
Denis V. Lunev (7):
doc: sync help description for --trace with man for qemu.1
doc: move text describing --trace to specific .texi file
trace: move qemu_trace_opts to trace/control.c
trace: enable tracing in qemu-io
trace: enable tracing in qemu-nbd
qemu-img: move common options parsing before commands processing
trace: enable tracing in qemu-img
Lluís Vilanova (1):
trace: [*-user] Add events to trace guest syscalls in syscall
emulation mode
Makefile | 7 +++---
bsd-user/syscall.c | 9 ++++++++
linux-user/syscall.c | 2 ++
qemu-img.c | 58 ++++++++++++++++++++++++++++++++++++++------------
qemu-img.texi | 13 ++++++++++-
qemu-io.c | 18 ++++++++++++----
qemu-nbd.c | 19 ++++++++++++++++-
qemu-nbd.texi | 3 +++
qemu-option-trace.texi | 25 ++++++++++++++++++++++
qemu-options.hx | 29 ++-----------------------
trace-events | 16 ++++++++++++++
trace/control.c | 42 +++++++++++++++++++++++++++++++++++-
trace/control.h | 25 ++++++++++++----------
vl.c | 38 ++-------------------------------
14 files changed, 206 insertions(+), 98 deletions(-)
create mode 100644 qemu-option-trace.texi
--
2.7.4
next reply other threads:[~2016-06-28 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 21:27 Stefan Hajnoczi [this message]
2016-06-28 21:27 ` [Qemu-devel] [PULL 1/8] doc: sync help description for --trace with man for qemu.1 Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 2/8] doc: move text describing --trace to specific .texi file Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 3/8] trace: move qemu_trace_opts to trace/control.c Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 4/8] trace: enable tracing in qemu-io Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 5/8] trace: enable tracing in qemu-nbd Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 6/8] qemu-img: move common options parsing before commands processing Stefan Hajnoczi
2016-06-29 8:22 ` Denis V. Lunev
2016-07-01 16:39 ` Eric Blake
2016-06-28 21:27 ` [Qemu-devel] [PULL 7/8] trace: enable tracing in qemu-img Stefan Hajnoczi
2016-06-28 21:27 ` [Qemu-devel] [PULL 8/8] trace: [*-user] Add events to trace guest syscalls in syscall emulation mode Stefan Hajnoczi
2016-06-29 15:08 ` [Qemu-devel] [PULL 0/8] Tracing patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 21:31 Stefan Hajnoczi
2016-09-29 18:47 ` 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=1467149250-31165-1-git-send-email-stefanha@redhat.com \
--to=stefanha@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).