From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v4 0/2] trace: Add event for vCPU memory accesses
Date: Tue, 31 May 2016 15:33:25 -0700 [thread overview]
Message-ID: <20160531223325.GE24392@stefanha-x1.localdomain> (raw)
In-Reply-To: <146436485327.18188.3967167989618604187.stgit@fimbulvetr.bsc.es>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Fri, May 27, 2016 at 06:00:53PM +0200, Lluís Vilanova wrote:
> This series adds an event to track information related to memory accesses
> performed by the guest CPUs ("guest_mem_before").
>
> A future series might extend this to contain the physical address and memory
> value (e.g., "guest_mem_after").
>
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
>
> Changes in v4
> -------------
>
> * Clarify alignment info is not on the trace.
> * Add event information on commit log. [Richard Henderson]
I'm happy to merge once TCG folks have reviewed it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-31 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 16:00 [Qemu-devel] [PATCH v4 0/2] trace: Add event for vCPU memory accesses Lluís Vilanova
2016-05-27 16:00 ` [Qemu-devel] [PATCH v4 1/2] exec: [tcg] Track which vCPU is performing translation and execution Lluís Vilanova
2016-05-27 16:01 ` [Qemu-devel] [PATCH v4 2/2] trace: [all] Add "guest_mem_before" event Lluís Vilanova
2016-06-09 16:39 ` Richard Henderson
2016-06-09 17:07 ` Lluís Vilanova
2016-05-31 22:33 ` Stefan Hajnoczi [this message]
2016-06-09 13:04 ` [Qemu-devel] [PATCH v4 0/2] trace: Add event for vCPU memory accesses Stefan Hajnoczi
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=20160531223325.GE24392@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).