From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Lluís Vilanova" <vilanova@imperial.ac.uk>,
matheus.ferst@eldorado.org.br,
"Laurent Vivier" <laurent@vivier.eu>,
qemu-devel@nongnu.org
Subject: Re: trace_FOO_tcg bit-rotted?
Date: Tue, 13 Apr 2021 10:25:39 +0100 [thread overview]
Message-ID: <87o8eimszx.fsf@linaro.org> (raw)
In-Reply-To: <YHVXSJs6JpCnSvqw@stefanha-x1.localdomain>
Stefan Hajnoczi <stefanha@redhat.com> writes:
> On Mon, Apr 12, 2021 at 08:06:57PM +0100, Alex Bennée wrote:
>>
>> Stefan Hajnoczi <stefanha@redhat.com> writes:
>>
>> > On Fri, Apr 09, 2021 at 05:29:08PM +0100, Alex Bennée wrote:
>> >>
>> >> Laurent Vivier <laurent@vivier.eu> writes:
>> >>
>> >> > Le 06/04/2021 à 18:00, Alex Bennée a écrit :
>> >> >> Hi,
>> >> >>
>> >> >> It's been awhile since I last played with this but I think we are
>> >> >> suffering from not having some test cases for tracing code
>> >> >> generation/execution in the tree. I tried adding a simple trace point to
>> >> >> see if I could track ERET calls:
<snip>
>> >
>> > Lluís: are you happy to deprecate tcg trace events in favor of TCG
>> > plugins?
<snip>
>
> That said, I haven't used the TCG trace event functionality and maybe
> I'm missing something obvious that Lluís will point out :).
I've updated the Cc to what I think is Lluís current email as I was
getting bounces from the old academic address.
--
Alex Bennée
next prev parent reply other threads:[~2021-04-13 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 16:00 trace_FOO_tcg bit-rotted? Alex Bennée
2021-04-06 17:24 ` no-reply
2021-04-07 9:08 ` Laurent Vivier
2021-04-09 16:29 ` Alex Bennée
2021-04-12 15:00 ` Stefan Hajnoczi
2021-04-12 19:06 ` Alex Bennée
2021-04-13 8:33 ` Stefan Hajnoczi
2021-04-13 9:25 ` Alex Bennée [this message]
2021-04-23 10:58 ` Vilanova, Lluis
2021-04-23 15:14 ` Alex Bennée
2021-04-27 13:00 ` Vilanova, Lluis
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=87o8eimszx.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--cc=matheus.ferst@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@imperial.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.