Re: [PATCH v2 3/6] cputlb: ensure we save the IOTLB data in case of reset

2020-06-22 Thread Emilio G. Cota
On Mon, Jun 22, 2020 at 10:02:50 +0100, Alex Bennée wrote: > Emilio G. Cota writes: > > On Wed, Jun 10, 2020 at 16:55:06 +0100, Alex Bennée wrote: (snip) > >> +#ifdef CONFIG_PLUGIN > >> + > >> +typedef struct SavedIOTLB { > >> +struct rcu_head rcu; > >> +struct SavedIOTLB **save_loc; > >>

Re: [PATCH v2 3/6] cputlb: ensure we save the IOTLB data in case of reset

2020-06-22 Thread Alex Bennée
Emilio G. Cota writes: > On Wed, Jun 10, 2020 at 16:55:06 +0100, Alex Bennée wrote: >> Any write to a device might cause a re-arrangement of memory >> triggering a TLB flush and potential re-size of the TLB invalidating >> previous entries. This would cause users of qemu_plugin_get_hwaddr() >>

Re: [PATCH v2 3/6] cputlb: ensure we save the IOTLB data in case of reset

2020-06-21 Thread Emilio G. Cota
On Wed, Jun 10, 2020 at 16:55:06 +0100, Alex Bennée wrote: > Any write to a device might cause a re-arrangement of memory > triggering a TLB flush and potential re-size of the TLB invalidating > previous entries. This would cause users of qemu_plugin_get_hwaddr() > to see the warning: > >

[PATCH v2 3/6] cputlb: ensure we save the IOTLB data in case of reset

2020-06-10 Thread Alex Bennée
Any write to a device might cause a re-arrangement of memory triggering a TLB flush and potential re-size of the TLB invalidating previous entries. This would cause users of qemu_plugin_get_hwaddr() to see the warning: invalid use of qemu_plugin_get_hwaddr because of the failed tlb_lookup