> This really isn't what the plugin API is intended for -- it's meant
>
> for tracing and similar sorts of "track what the guest is doing" activities.
>
> If you want to model an MMIO device, you're better off just writing a device
>
> model like any of the others in QEMU, I think: the APIs for doi
Thank you for you answer.
> Out of interest what is your use-case for this? The project has very
>
> deliberately avoided adding such an API for writing memory for plugins
>
> to avoid people attempting to bypass the GPL by doing things in plugins.
>
In the scope of my Ph. D subject, I want to mo
On Fri, 25 Jun 2021 at 10:25, Kevin Mambu wrote:
> In the scope of my Ph. D subject, I want to model a DMA-like mechanism for
> quick prototyping and evaluation, the plugin emulates an MMIO with
> Control/Status Registers. I am actually able to pass parameters to the
> Control/Status Registers
Philippe Mathieu-Daudé writes:
> Cc'ing the maintainer: Alex.
>
> On 6/23/21 5:08 PM, Kevin Mambu wrote:
>> Hi, everyone,
>> I need to put in place a plugin which is able to modify memory for a
>> specific project, and until now I managed to do so using
>> cpu_memory_rw_debug().
Out of interes
Cc'ing the maintainer: Alex.
On 6/23/21 5:08 PM, Kevin Mambu wrote:
> Hi, everyone,
> I need to put in place a plugin which is able to modify memory for a
> specific project, and until now I managed to do so using
> cpu_memory_rw_debug().
> However, the function happens to fail at times, and when
