Re: [dpdk-dev] [PATCH] vhost: protect log addr translation in iotlb updates

2020-02-13 Thread Maxime Coquelin
On 2/13/20 5:18 PM, Maxime Coquelin wrote: > > > On 2/13/20 11:04 AM, Adrian Moreno wrote: >> Currently, the log address translation only happens in the vhost-user's >> translate_ring_addresses(). However, the IOTLB update handler is not >> checking if it was mapped to re-trigger that transla

Re: [dpdk-dev] [PATCH] vhost: protect log addr translation in iotlb updates

2020-02-13 Thread Maxime Coquelin
On 2/13/20 11:04 AM, Adrian Moreno wrote: > Currently, the log address translation only happens in the vhost-user's > translate_ring_addresses(). However, the IOTLB update handler is not > checking if it was mapped to re-trigger that translation. > > Since the log address mapping could fail, c

Re: [dpdk-dev] [PATCH] vhost: protect log addr translation in iotlb updates

2020-02-13 Thread Adrian Moreno
On 2/13/20 12:09 PM, Kevin Traynor wrote: > On 13/02/2020 10:04, Adrian Moreno wrote: >> Currently, the log address translation only happens in the vhost-user's >> translate_ring_addresses(). However, the IOTLB update handler is not >> checking if it was mapped to re-trigger that translation. >> >

Re: [dpdk-dev] [PATCH] vhost: protect log addr translation in iotlb updates

2020-02-13 Thread Kevin Traynor
On 13/02/2020 10:04, Adrian Moreno wrote: > Currently, the log address translation only happens in the vhost-user's > translate_ring_addresses(). However, the IOTLB update handler is not > checking if it was mapped to re-trigger that translation. > > Since the log address mapping could fail, chec

[dpdk-dev] [PATCH] vhost: protect log addr translation in iotlb updates

2020-02-13 Thread Adrian Moreno
Currently, the log address translation only happens in the vhost-user's translate_ring_addresses(). However, the IOTLB update handler is not checking if it was mapped to re-trigger that translation. Since the log address mapping could fail, check it on iotlb updates. Also, check it on vring_trans