On 27 September 2017 at 15:56, Eric Auger <eric.au...@redhat.com> wrote: > The ITS is not properly reset at the moment. It is possible the > GITS_BASER<n>.valid is set and the in-kernel ITS caches are not > empty (list of devices, collections, LPIs) while data structures > in guest RAM are invalid/inconsistent. > > For instance, this happens after a guest shutdown -r now or a > system reset, if we save the state before the guest re-writes > the ITS registers or map devices, the table save ioctl may > produce a QEMU abort. > > Until there is a proper reset implemented, let's unplug the > consistency error checking. > > The reset issue will be fixed in subsequent patches. > > Signed-off-by: Eric Auger <eric.au...@redhat.com> > Reported-by: wanghaibin <wanghaibin.w...@huawei.com>
When in particular does this cause an abort -- when we're trying to save the state in these edge cases, or when we're trying to restore it? What does the kernel do -- is it just rejecting the attempt, or might it actually have done bad things to guest memory ? thanks -- PMM
