On 9/9/24 13:21, Alex Bennée wrote:
Pierrick Bouvier writes:
On 9/9/24 03:00, Alex Bennée wrote:
Pierrick Bouvier writes:
On 9/5/24 08:21, Alex Bennée wrote:
Pierrick Bouvier writes:
This series allows plugins to know which value is read/written during a memory
access.
For every memor
Pierrick Bouvier writes:
> On 9/9/24 03:00, Alex Bennée wrote:
>> Pierrick Bouvier writes:
>>
>>> On 9/5/24 08:21, Alex Bennée wrote:
Pierrick Bouvier writes:
> This series allows plugins to know which value is read/written during a
> memory
> access.
>
> For eve
On 9/9/24 03:00, Alex Bennée wrote:
Pierrick Bouvier writes:
On 9/5/24 08:21, Alex Bennée wrote:
Pierrick Bouvier writes:
This series allows plugins to know which value is read/written during a memory
access.
For every memory access, we know copy this value before calling mem callbacks,
a
Pierrick Bouvier writes:
> On 9/5/24 08:21, Alex Bennée wrote:
>> Pierrick Bouvier writes:
>>
>>> This series allows plugins to know which value is read/written during a
>>> memory
>>> access.
>>>
>>> For every memory access, we know copy this value before calling mem
>>> callbacks,
>>> and t
On 9/5/24 08:21, Alex Bennée wrote:
Pierrick Bouvier writes:
This series allows plugins to know which value is read/written during a memory
access.
For every memory access, we know copy this value before calling mem callbacks,
and those can query it using new API function:
- qemu_plugin_mem_g
Pierrick Bouvier writes:
> This series allows plugins to know which value is read/written during a memory
> access.
>
> For every memory access, we know copy this value before calling mem callbacks,
> and those can query it using new API function:
> - qemu_plugin_mem_get_value
Queued to patches
This series allows plugins to know which value is read/written during a memory
access.
For every memory access, we know copy this value before calling mem callbacks,
and those can query it using new API function:
- qemu_plugin_mem_get_value
Mem plugin was extended to print accesses, and a new tes
