lkml.org 
[lkml]   [2016]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] vfio/iommu_type1: make use of info.flags
From
Date
On Wed, 2015-12-23 at 13:08 +0100, Pierre Morel wrote:
> The flags entry is there to tell the user that some
> optional information is available.
>
> Since we report the iova_pgsizes signal it to the user
> by setting the flags to VFIO_IOMMU_INFO_PGSIZES.
>
> Signed-off-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
> ---
>  drivers/vfio/vfio_iommu_type1.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c
> b/drivers/vfio/vfio_iommu_type1.c
> index 59d47cb..6f1ea3d 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -995,7 +995,7 @@ static long vfio_iommu_type1_ioctl(void
> *iommu_data,
>   if (info.argsz < minsz)
>   return -EINVAL;
>  
> - info.flags = 0;
> + info.flags = VFIO_IOMMU_INFO_PGSIZES;
>  
>   info.iova_pgsizes = vfio_pgsize_bitmap(iommu);
>  

Applied to my next branch for v4.5, thanks!

Alex

PS - I haven't lost your qemu overflow patch, sorry for the delay.


\
 
 \ /
  Last update: 2016-01-05 01:01    [W:0.184 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site