On 10/05/2016 03:06 AM, Lluís Vilanova wrote:
Richard Henderson writes:
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
Richard Henderson writes:
> 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. A
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
gues
Richard Henderson writes:
> On 09/28/2016 06:21 AM, Lluís Vilanova wrote:
>> Hi! I've kept working on extending the guest instruction tracing features,
>> and
>> added support to trace which registers are read/written by guest instructions
>> (when executing with TCG).
>>
>> I've basically exten
On 09/28/2016 06:21 AM, Lluís Vilanova wrote:
> Hi! I've kept working on extending the guest instruction tracing features, and
> added support to trace which registers are read/written by guest instructions
> (when executing with TCG).
>
> I've basically extended "tcg_global_mem_new_*" to associat
Hi! I've kept working on extending the guest instruction tracing features, and
added support to trace which registers are read/written by guest instructions
(when executing with TCG).
I've basically extended "tcg_global_mem_new_*" to associate global TCG registers
with a guest (vCPU) register numb
