> > Do you mean concurrent access to the same memory block by multiple
> > threads?
>
> Yes - although we also see MMU changes updating a mapping for a given
> vaddr -> phys address.
>
> >
> > I think , for guest threads/cores if we observe mismatch of memory content
> > read by a plugin and ins
Mikhail Tyutin writes:
>> Not sure what happened with the formatting of this patch, I think there
>> is an html part getting in the way.
> I guess line ends were messed up somewhere on my side. Will try to figure out
> the root cause.
>
>
>> > +qemu_plugin_vcpu_read_phys_mem(vcpuIndex, vad
> Not sure what happened with the formatting of this patch, I think there
> is an html part getting in the way.
I guess line ends were messed up somewhere on my side. Will try to figure out
the root cause.
> > +qemu_plugin_vcpu_read_phys_mem(vcpuIndex, vaddr, memContent,
> > size);
>
> So t
Mikhail Tyutin writes:
> TCG plugin API extension to read guest memory content.
> qemu_plugin_vcpu_read_phys_mem()
>
> function can be used by TCG plugin inside of qemu_plugin_vcpu_mem_cb_t
> callback to adjust
>
> received address according to internal memory mappings and read content of
>