Re: [PATCH 1/1] kvm/book3s_64: Fixes crash caused by not cleaning vhost IOTLB

2019-12-19 Thread Alexey Kardashevskiy
On 19/12/2019 10:28, Leonardo Bras wrote: > On Wed, 2019-12-18 at 15:53 +1100, Alexey Kardashevskiy wrote: >> H_STUFF_TCE is always called with 0. Well, may be some AIX somewhere >> calls it with a value other than zero, and I probably saw some other >> value somewhere but in QEMU/KVM case it

Re: [PATCH 1/1] kvm/book3s_64: Fixes crash caused by not cleaning vhost IOTLB

2019-12-18 Thread Leonardo Bras
On Wed, 2019-12-18 at 15:53 +1100, Alexey Kardashevskiy wrote: > H_STUFF_TCE is always called with 0. Well, may be some AIX somewhere > calls it with a value other than zero, and I probably saw some other > value somewhere but in QEMU/KVM case it is 0 so you effectively disable > in-kernel

Re: [PATCH 1/1] kvm/book3s_64: Fixes crash caused by not cleaning vhost IOTLB

2019-12-17 Thread Alexey Kardashevskiy
On 18/12/2019 08:06, Leonardo Bras wrote: > Fixes a bug that happens when a virtual machine is created without DDW, > with vhost supporting a virtio-net device. > > In this scenario, an IOMMU with 32-bit DMA window will possibly map > IOVA's to different memory addresses. > > As the code

[PATCH 1/1] kvm/book3s_64: Fixes crash caused by not cleaning vhost IOTLB

2019-12-17 Thread Leonardo Bras
Fixes a bug that happens when a virtual machine is created without DDW, with vhost supporting a virtio-net device. In this scenario, an IOMMU with 32-bit DMA window will possibly map IOVA's to different memory addresses. As the code works today, H_STUFF_TCE hypercall will be dealt only with kvm