On 03/07/20 09:39, Eugenio Perez Martin wrote:
> #4 0x55888171 in memory_region_notify_one
> (notifier=0x7ffde0487fa8, entry=0x7ffde5dfe200) at
> /home/qemu/memory.c:1918
> 1918assert(entry->iova >= notifier->start && entry_end <=
> notifier->end);
> (gdb) p *entry
> $1 = {target_a
On Mon, Jun 29, 2020 at 5:05 PM Paolo Bonzini wrote:
>
> On 26/06/20 08:41, Eugenio Pérez wrote:
> > If we examinate *entry in frame 4 of backtrace:
> > *entry = {target_as = 0x56f6c050, iova = 0x0, translated_addr = 0x0,
> > addr_mask = 0x, perm = 0x0}
> >
> > Which (I think)
On 26/06/20 08:41, Eugenio Pérez wrote:
> If we examinate *entry in frame 4 of backtrace:
> *entry = {target_as = 0x56f6c050, iova = 0x0, translated_addr = 0x0,
> addr_mask = 0x, perm = 0x0}
>
> Which (I think) tries to invalidate all the TLB registers of the device.
>
> Just
I am able to hit this assertion when a Red Hat 7 guest virtio_net device
raises an "Invalidation" of all the TLB entries. This happens in the
guest's startup if 'intel_iommu=on' argument is passed to the guest
kernel and right IOMMU/ATS devices are declared in qemu's command line.
Command line:
/h
