Re: [PATCH] vfio/type1: Restore mapping performance with mdev support

2016-12-16 Thread Kirti Wankhede
On 12/15/2016 11:57 PM, Alex Williamson wrote: > On Thu, 15 Dec 2016 23:27:54 +0530 > Kirti Wankhede wrote: > >> On 12/15/2016 1:33 PM, Alex Williamson wrote: >>> On Thu, 15 Dec 2016 12:05:35 +0530 >>> Kirti Wankhede wrote: >>> On 12/14/2016 2:28 AM, Alex Williamson wrote: > As p

Re: [PATCH] vfio/type1: Restore mapping performance with mdev support

2016-12-15 Thread Alex Williamson
On Thu, 15 Dec 2016 23:27:54 +0530 Kirti Wankhede wrote: > On 12/15/2016 1:33 PM, Alex Williamson wrote: > > On Thu, 15 Dec 2016 12:05:35 +0530 > > Kirti Wankhede wrote: > > > >> On 12/14/2016 2:28 AM, Alex Williamson wrote: > >>> As part of the mdev support, type1 now gets a task reference

Re: [PATCH] vfio/type1: Restore mapping performance with mdev support

2016-12-15 Thread Kirti Wankhede
On 12/15/2016 1:33 PM, Alex Williamson wrote: > On Thu, 15 Dec 2016 12:05:35 +0530 > Kirti Wankhede wrote: > >> On 12/14/2016 2:28 AM, Alex Williamson wrote: >>> As part of the mdev support, type1 now gets a task reference per >>> vfio_dma and uses that to get an mm reference for the task while

Re: [PATCH] vfio/type1: Restore mapping performance with mdev support

2016-12-15 Thread Alex Williamson
On Thu, 15 Dec 2016 12:05:35 +0530 Kirti Wankhede wrote: > On 12/14/2016 2:28 AM, Alex Williamson wrote: > > As part of the mdev support, type1 now gets a task reference per > > vfio_dma and uses that to get an mm reference for the task while > > working on accounting. That's the correct thing t

Re: [PATCH] vfio/type1: Restore mapping performance with mdev support

2016-12-14 Thread Kirti Wankhede
On 12/14/2016 2:28 AM, Alex Williamson wrote: > As part of the mdev support, type1 now gets a task reference per > vfio_dma and uses that to get an mm reference for the task while > working on accounting. That's the correct thing to do for paths > where we can't rely on using current, but there