From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 00/12] trace: [tcg] Allow tracing guest events in TCG-generated code
Date: Fri, 07 Feb 2014 06:49:35 -0800 [thread overview]
Message-ID: <52F4F27F.5000703@twiddle.net> (raw)
In-Reply-To: <87a9e411r9.fsf@fimbulvetr.bsc.es>
On 02/06/2014 11:26 AM, Lluís Vilanova wrote:
>> > At which point, option 2 would be the best bet, I think.
> Right. For the 3rd option I was also thinking about having per-vCPU tracing
> states (in the case of guest events), so that you can trace separate events
> depending on the vCPU.
>
> Which reminds me, I should add a vCPU pointer to the "guest_vmem" event, since
> otherwise you cannot differentiate accesses among different vCPUs.
The TB cache is shared, so you won't be able to do option 3 for different
events for different cpus. You could only do option 1 for that.
r~
next prev parent reply other threads:[~2014-02-07 14:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 16:09 [Qemu-devel] [PATCH 00/12] trace: [tcg] Allow tracing guest events in TCG-generated code Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 01/12] trace: [tcg] Add documentation Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 02/12] trace: [tracetool, tcg] Allow TCG types in trace event declarations Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 03/12] trace: [tracetool] Add method 'Event.api' to get the name of public routines Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 04/12] trace: [tracetool, tcg] Provide TCG-related type transformation rules Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 05/12] trace: [tracetool] Allow argument types to be transformed Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 06/12] trace: [tcg] Declare TCG tracing helper routines Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 07/12] trace: [tcg] Define " Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 08/12] trace: [tcg] Include TCG-tracing helpers on all helper.h Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 09/12] trace: [tcg] Generate TCG tracing routines Lluís Vilanova
2014-01-31 16:09 ` [Qemu-devel] [PATCH 10/12] trace: [trivial] Include event definitions in "trace.h" Lluís Vilanova
2014-01-31 16:10 ` [Qemu-devel] [PATCH 11/12] trace: [tcg] Include TCG-tracing header on all targets Lluís Vilanova
2014-01-31 16:10 ` [Qemu-devel] [PATCH 12/12] trace: [all] Add "guest_vmem" event Lluís Vilanova
2014-02-04 15:08 ` Richard Henderson
2014-02-04 20:01 ` Lluís Vilanova
2014-02-06 16:12 ` Richard Henderson
2014-02-10 13:29 ` Lluís Vilanova
2014-02-03 14:40 ` [Qemu-devel] [PATCH 00/12] trace: [tcg] Allow tracing guest events in TCG-generated code Stefan Hajnoczi
2014-02-03 16:24 ` Lluís Vilanova
2014-02-04 14:57 ` Richard Henderson
2014-02-04 15:02 ` Peter Maydell
2014-02-04 15:17 ` Richard Henderson
2014-02-04 20:44 ` Lluís Vilanova
2014-02-04 20:34 ` Lluís Vilanova
2014-02-04 20:33 ` Lluís Vilanova
2014-02-06 15:57 ` Richard Henderson
2014-02-06 19:26 ` Lluís Vilanova
2014-02-07 14:49 ` Richard Henderson [this message]
2014-02-07 15:13 ` Peter Maydell
2014-02-07 15:24 ` 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=52F4F27F.5000703@twiddle.net \
--to=rth@twiddle.net \
--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).