Hi Peter, On 23/11/17 16:19, Peter Maydell wrote: > On 23 November 2017 at 14:56, Eric Auger <eric.au...@redhat.com> wrote: >> At the moment the ITS is not properly reset. On System reset or >> reboot, previous ITS register values and caches are left >> unchanged. Some of the registers might point to some guest RAM >> tables which are not valid anymore. This leads to state >> inconsistencies that are detected by the kernel save/restore >> code. And eventually this may cause qemu abort. >> >> This series adds vITS reset modality: >> - the 2 first patches bring a minimalist reset through individual >> register writes. However, with kernel versions < 4.15, this reset >> is not complete (vITS caches are not voided). >> - With kernel versions >= 4.15 we can rely on a new ITS KVM device >> reset IOTCL. The last 2 patches introduce the full reset. >> >> Patches 1-2 have all kernel dependencies resolved. >> Patches 3-4' dependencies were pulled for v4.15-rc0 but as the tag is >> not set, the kernel header update still is partial. > > We don't need the change to be tagged for us to sync with the > kernel headers: if it's in mainline that's good enough.
OK. do you allow me to keep a partial update for: linux-headers/asm-arm/kvm.h linux-headers/asm-arm64/kvm.h? When using update-linux-headers.sh I get suspicious errors at the end: grep: /tmp/tmp.A5NjLtHOij/include/asm/kvm_virtio.h: No such file or directory sed: can't read /tmp/tmp.A5NjLtHOij/include/asm/kvm_virtio.h: No such file or directory and include/standard-headers/asm-s390/virtio-ccw.h deleted I would prefer having s390 people checking and testing that. Thanks Eric > > thanks > -- PMM >
