On Mon, 3 Jun 2019 at 21:36, Christophe Lyon wrote:
>
> On Thu, 30 May 2019 at 12:28, Alex Bennée wrote:
> >
> >
> > Hi,
> >
> > Food for thought for today's sync up. I've been writting QEMU plugins to
> > exercise the plugin system and see what sort of useful information you
> > can extract when
On Thu, 30 May 2019 at 12:28, Alex Bennée wrote:
>
>
> Hi,
>
> Food for thought for today's sync up. I've been writting QEMU plugins to
> exercise the plugin system and see what sort of useful information you
> can extract when you can control the instruction stream.
>
> For example I now have a p
On Thu, 30 May 2019 at 11:28, Alex Bennée wrote:
>
>
> Hi,
>
> Food for thought for today's sync up. I've been writting QEMU plugins to
> exercise the plugin system and see what sort of useful information you
> can extract when you can control the instruction stream.
>
> For example I now have a p
On 30/05/2019 07:27, Alex Bennée wrote:
>
> Hi,
>
> Food for thought for today's sync up. I've been writting QEMU plugins to
> exercise the plugin system and see what sort of useful information you
> can extract when you can control the instruction stream.
>
> For example I now have a plugin t
Hi,
Food for thought for today's sync up. I've been writting QEMU plugins to
exercise the plugin system and see what sort of useful information you
can extract when you can control the instruction stream.
For example I now have a plugin that can break down instruction counts
for any given run, f
