Re: Plugin Register Accesses

2021-01-07 Thread Aaron Lindsay via
On Jan 07 16:49, Alex Bennée wrote: > > Aaron Lindsay writes: > > > On Dec 08 14:44, Aaron Lindsay wrote: > >> On Dec 08 17:56, Alex Bennée wrote: > >> > Aaron Lindsay writes: > >> > > On Dec 08 12:17, Alex Bennée wrote: > >> > >> Aaron Lindsay writes: > >> > >> Memory is a little trickier b

Re: Plugin Register Accesses

2021-01-07 Thread Alex Bennée
Aaron Lindsay writes: > On Dec 08 14:44, Aaron Lindsay wrote: >> On Dec 08 17:56, Alex Bennée wrote: >> > Aaron Lindsay writes: >> > > On Dec 08 12:17, Alex Bennée wrote: >> > >> Aaron Lindsay writes: >> > >> Memory is a little trickier because you can't know at any point if a >> > >> giv

Re: Plugin Register Accesses

2020-12-30 Thread Aaron Lindsay via
On Dec 08 14:44, Aaron Lindsay wrote: > On Dec 08 17:56, Alex Bennée wrote: > > Aaron Lindsay writes: > > > On Dec 08 12:17, Alex Bennée wrote: > > >> Aaron Lindsay writes: > > >> Memory is a little trickier because you can't know at any point if a > > >> given virtual address is actually map

Re: Plugin Register Accesses

2020-12-08 Thread Alex Bennée
Aaron Lindsay writes: > On Dec 08 17:56, Alex Bennée wrote: >> Aaron Lindsay writes: >> > On Dec 08 12:17, Alex Bennée wrote: >> >> For registers I think there needs to be some re-factoring of QEMU's >> >> internals to do it cleanly. Currently we have each front-end providing >> >> hooks

Re: Plugin Register Accesses

2020-12-08 Thread Aaron Lindsay via
On Dec 08 17:56, Alex Bennée wrote: > Aaron Lindsay writes: > > On Dec 08 12:17, Alex Bennée wrote: > >> For registers I think there needs to be some re-factoring of QEMU's > >> internals to do it cleanly. Currently we have each front-end providing > >> hooks to the gdbstub as well as buildi

Re: Plugin Register Accesses

2020-12-08 Thread Aaron Lindsay via
On Dec 08 17:56, Alex Bennée wrote: > Aaron Lindsay writes: > > On Dec 08 12:17, Alex Bennée wrote: > >> Aaron Lindsay writes: > >> Memory is a little trickier because you can't know at any point if a > >> given virtual address is actually mapped to real memory. The safest way > >> would be

Re: Plugin Register Accesses

2020-12-08 Thread Alex Bennée
Aaron Lindsay writes: > On Dec 08 12:17, Alex Bennée wrote: >> Aaron Lindsay writes: >> >> > I'm trying to migrate to using the new plugin interface. I see the >> > following in include/qemu/qemu-plugin.h: >> > >> >> enum qemu_plugin_cb_flags { >> >> QEMU_PLUGIN_CB_NO_REGS, /* callback do

Re: Plugin Register Accesses

2020-12-08 Thread Aaron Lindsay via
On Dec 08 12:17, Alex Bennée wrote: > Aaron Lindsay writes: > > > I'm trying to migrate to using the new plugin interface. I see the > > following in include/qemu/qemu-plugin.h: > > > >> enum qemu_plugin_cb_flags { > >> QEMU_PLUGIN_CB_NO_REGS, /* callback does not access the CPU's regs */ > >

Re: Plugin Register Accesses

2020-12-08 Thread Alex Bennée
Aaron Lindsay writes: > I'm trying to migrate to using the new plugin interface. I see the > following in include/qemu/qemu-plugin.h: > >> enum qemu_plugin_cb_flags { >> QEMU_PLUGIN_CB_NO_REGS, /* callback does not access the CPU's regs */ >> QEMU_PLUGIN_CB_R_REGS, /* callback reads th

Plugin Register Accesses

2020-12-07 Thread Aaron Lindsay
I'm trying to migrate to using the new plugin interface. I see the following in include/qemu/qemu-plugin.h: > enum qemu_plugin_cb_flags { > QEMU_PLUGIN_CB_NO_REGS, /* callback does not access the CPU's regs */ > QEMU_PLUGIN_CB_R_REGS, /* callback reads the CPU's regs */ > QEMU_PLUGIN_