From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC] Tracing guest register usage
Date: Fri, 30 Sep 2016 11:56:34 -0700 [thread overview]
Message-ID: <cfd92f66-83c8-81b9-e501-3f447d26fe4e@twiddle.net> (raw)
In-Reply-To: <87r381ju8h.fsf@fimbulvetr.bsc.es>
On 09/30/2016 08:13 AM, Lluís Vilanova wrote:
>> (2) an internal state change
>> to DisasContext, reflected in INDEX_op_insn_start, with no changes to any TCG
>> registers. So you'll not actually be tracking eflags at all.
>
> I don't follow what you mean. AFAIK INDEX_op_insn_start does not change the
> guest eflags.
It sets cc_op, which affects how eflags is computed.
r~
next prev parent reply other threads:[~2016-09-30 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 13:21 [Qemu-devel] [RFC] Tracing guest register usage Lluís Vilanova
2016-09-28 17:18 ` Richard Henderson
2016-09-30 15:13 ` Lluís Vilanova
2016-09-30 18:56 ` Richard Henderson [this message]
2016-10-05 10:06 ` Lluís Vilanova
2016-10-05 16:16 ` Richard Henderson
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=cfd92f66-83c8-81b9-e501-3f447d26fe4e@twiddle.net \
--to=rth@twiddle.net \
--cc=crosthwaite.peter@gmail.com \
--cc=pbonzini@redhat.com \
--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).