Re: [PATCH] vfio/iommu_type1: make use of info.flags

[Alex Williamson]

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@xxxxxxxxxxxxxxxxxx>
> ---
> Â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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/