[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACGkMEvkHKqOkTCEaTUHK4Ve=naeU5p09BpnvPW-y1cGqOTo_w@mail.gmail.com>
Date: Fri, 8 Jul 2022 11:14:13 +0800
From: Jason Wang <jasowang@...hat.com>
To: Robin Murphy <robin.murphy@....com>
Cc: mst <mst@...hat.com>, kvm <kvm@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>,
netdev <netdev@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vdpa: Use device_iommu_capable()
On Wed, Jun 8, 2022 at 7:53 PM Robin Murphy <robin.murphy@....com> wrote:
>
> Use the new interface to check the capability for our device
> specifically.
>
> Signed-off-by: Robin Murphy <robin.murphy@....com>
Acked-by: Jason Wang <jasowang@...hat.com>
> ---
> drivers/vhost/vdpa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
> index 935a1d0ddb97..4cfebcc24a03 100644
> --- a/drivers/vhost/vdpa.c
> +++ b/drivers/vhost/vdpa.c
> @@ -1074,7 +1074,7 @@ static int vhost_vdpa_alloc_domain(struct vhost_vdpa *v)
> if (!bus)
> return -EFAULT;
>
> - if (!iommu_capable(bus, IOMMU_CAP_CACHE_COHERENCY))
> + if (!device_iommu_capable(dma_dev, IOMMU_CAP_CACHE_COHERENCY))
> return -ENOTSUPP;
>
> v->domain = iommu_domain_alloc(bus);
> --
> 2.36.1.dirty
>
Powered by blists - more mailing lists