or 3 days on
qemu+plugins and only observed a tolerable growth in qemu's memory consumption.
From: Alex Bennée
Sent: Friday, January 24, 2020 11:44 AM
To: Robert Henry
Cc: Laurent Desnogues ; qemu-devel@nongnu.org
Subject: Re: [EXTERNAL] Re: QEMU for aarch
Robert Henry writes:
> I found at least one problem with my plugin.
>
> I was assuming that the insn data from
> struct qemu_plugin_insn *insn = qemu_plugin_tb_get_insn(tb, i);
> could be passed into qemu_plugin_register_vcpu_insn_exec_cb both as the 1st
> argument AND as the user data l
with plugins seems to fail basic
consistency checks
Robert Henry writes:
> I wrote a QEMU plugin for aarch64 where the insn and mem callbacks
> print out the specifics of the guest instructions as they are
> "executed". I expect this trace stream to be well behaved but it is
&
Robert Henry writes:
> I wrote a QEMU plugin for aarch64 where the insn and mem callbacks
> print out the specifics of the guest instructions as they are
> "executed". I expect this trace stream to be well behaved but it is
> not.
Can you post your plugin? It's hard to diagnose what might be
Hello,
On Fri, Jan 24, 2020 at 1:45 AM Robert Henry wrote:
>
> I wrote a QEMU plugin for aarch64 where the insn and mem callbacks print out
> the specifics of the guest instructions as they are "executed". I expect
> this trace stream to be well behaved but it is not. By well-behaved, I expect
I wrote a QEMU plugin for aarch64 where the insn and mem callbacks print out
the specifics of the guest instructions as they are "executed". I expect this
trace stream to be well behaved but it is not. By well-behaved, I expect memory
insns print out some memory details, non-memory insns don't
