From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/5] trace: Add events for vCPU memory accesses
Date: Tue, 23 Feb 2016 19:22:07 +0100 [thread overview]
Message-ID: <145625172744.12025.2350972792125742783.stgit@localhost> (raw)
NOTE: This series applies on top of "trace: Show vCPU info in guest code events"
This series adds to new events:
* guest_vmem: memory accesses performed by vCPUs (guest code)
* guest_vmem_user_syscall: memory accesses performed by syscall emulation when
running QEMU in user-mode.
Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
---
Lluís Vilanova (5):
exec: [tcg] Track which vCPU is performing translation and execution
trace: [all] Add "guest_vmem" event
user: Refactor lock_user body into do_lock_user
user: Set current vCPU during syscall execution
trace: [all] Add "guest_vmem_user_syscall" event
bsd-user/qemu.h | 21 +++++++++++++++---
bsd-user/syscall.c | 2 ++
bsd-user/uaccess.c | 2 +-
include/exec/cpu_ldst_template.h | 17 +++++++++++++++
include/exec/cpu_ldst_useronly_template.h | 14 ++++++++++++
linux-user/qemu.h | 21 +++++++++++++++---
linux-user/syscall.c | 2 ++
linux-user/uaccess.c | 2 +-
target-alpha/translate.c | 1 +
target-arm/translate.c | 1 +
target-cris/translate.c | 1 +
target-cris/translate_v10.c | 1 +
target-i386/translate.c | 1 +
target-lm32/translate.c | 1 +
target-m68k/translate.c | 1 +
target-microblaze/translate.c | 1 +
target-mips/translate.c | 1 +
target-moxie/translate.c | 1 +
target-openrisc/translate.c | 1 +
target-ppc/translate.c | 1 +
target-s390x/translate.c | 1 +
target-sh4/translate.c | 1 +
target-sparc/translate.c | 1 +
target-tilegx/translate.c | 1 +
target-tricore/translate.c | 1 +
target-unicore32/translate.c | 1 +
target-xtensa/translate.c | 1 +
tcg/tcg-op.c | 34 ++++++++++++++++++++++++++---
tcg/tcg.h | 4 +++
trace-events | 23 ++++++++++++++++++++
translate-all.c | 2 ++
31 files changed, 151 insertions(+), 12 deletions(-)
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
next reply other threads:[~2016-02-23 18:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 18:22 Lluís Vilanova [this message]
2016-02-23 18:22 ` [Qemu-devel] [PATCH 1/5] exec: [tcg] Track which vCPU is performing translation and execution Lluís Vilanova
2016-03-16 15:01 ` Peter Maydell
2016-02-23 18:22 ` [Qemu-devel] [PATCH 2/5] trace: [all] Add "guest_vmem" event Lluís Vilanova
2016-03-16 15:01 ` Peter Maydell
2016-03-17 19:22 ` Lluís Vilanova
2016-03-17 20:18 ` Richard Henderson
2016-03-17 20:25 ` Peter Maydell
2016-03-18 18:50 ` Lluís Vilanova
2016-03-19 13:59 ` Peter Maydell
2016-03-20 18:09 ` Lluís Vilanova
2016-03-20 19:59 ` Peter Maydell
2016-03-21 16:51 ` Lluís Vilanova
2016-02-23 18:22 ` [Qemu-devel] [PATCH 3/5] user: Refactor lock_user body into do_lock_user Lluís Vilanova
2016-02-23 18:22 ` [Qemu-devel] [PATCH 4/5] user: Set current vCPU during syscall execution Lluís Vilanova
2016-02-23 18:22 ` [Qemu-devel] [PATCH 5/5] trace: [all] Add "guest_vmem_user_syscall" event Lluís Vilanova
2016-03-02 10:55 ` [Qemu-devel] [PATCH 0/5] trace: Add events for vCPU memory accesses Stefan Hajnoczi
2016-03-16 15:10 ` Peter Maydell
2016-03-22 12:55 ` Stefan Hajnoczi
2016-03-22 14:02 ` Lluís Vilanova
2016-03-22 14:47 ` Peter Maydell
2016-03-22 19:23 ` Lluís Vilanova
2016-03-22 20:23 ` Peter Maydell
2016-03-23 14:08 ` Lluís Vilanova
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=145625172744.12025.2350972792125742783.stgit@localhost \
--to=vilanova@ac.upc.edu \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).