From: Alex Williamson <alex.williamson@redhat.com>
To: Peng Fan <van.freenix@gmail.com>
Cc: b.reynal@virtualopensystems.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio: platform: use vfio_iommu_group_get/put
Date: Mon, 9 May 2016 09:32:38 -0600 [thread overview]
Message-ID: <20160509093238.3901f0b7@t450s.home> (raw)
In-Reply-To: <1462788103-19906-1-git-send-email-van.freenix@gmail.com>
On Mon, 9 May 2016 18:01:43 +0800
Peng Fan <van.freenix@gmail.com> wrote:
> Use vfio_iommu_group_get and vfio_iommu_group_put, but not
> iommu_group_get or iommu_group_put.
I assume you're trying to duplicate the vfio_pci changes from commit
03a76b60f8ba to enable no-iommu mode. That would be really relevant
information for the commit log.
>
> Signed-off-by: Peng Fan <van.freenix@gmail.com>
> Cc: Baptiste Reynal <b.reynal@virtualopensystems.com>
> Cc: Alex Williamson <alex.williamson@redhat.com>
> ---
> drivers/vfio/platform/vfio_platform_common.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/vfio/platform/vfio_platform_common.c b/drivers/vfio/platform/vfio_platform_common.c
> index e65b142..582885e 100644
> --- a/drivers/vfio/platform/vfio_platform_common.c
> +++ b/drivers/vfio/platform/vfio_platform_common.c
> @@ -561,7 +561,7 @@ int vfio_platform_probe_common(struct vfio_platform_device *vdev,
>
> vdev->device = dev;
>
> - group = iommu_group_get(dev);
> + group = vfio_iommu_group_get(dev);
> if (!group) {
> pr_err("VFIO: No IOMMU group for device %s\n", vdev->name);
> return -EINVAL;
> @@ -569,7 +569,7 @@ int vfio_platform_probe_common(struct vfio_platform_device *vdev,
>
> ret = vfio_add_group_dev(dev, &vfio_platform_ops, vdev);
> if (ret) {
> - iommu_group_put(group);
> + vfio_iommu_group_put(group);
> return ret;
> }
>
> @@ -589,7 +589,7 @@ struct vfio_platform_device *vfio_platform_remove_common(struct device *dev)
>
> if (vdev) {
> vfio_platform_put_reset(vdev);
> - iommu_group_put(dev->iommu_group);
> + vfio_iommu_group_put(dev->iommu_group, dev);
> }
>
> return vdev;
next prev parent reply other threads:[~2016-05-09 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 10:01 Peng Fan
2016-05-09 15:32 ` Alex Williamson [this message]
2016-05-10 7:40 ` Peng Fan
2016-05-19 21:01 ` Alex Williamson
2016-05-20 7:58 ` Eric Auger
2016-05-20 8:20 ` Baptiste Reynal
2016-05-20 8:36 ` Peng Fan
2016-05-20 9:22 ` Eric Auger
2016-05-20 9:56 ` Peng Fan
2016-05-20 16:19 ` Eric Auger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160509093238.3901f0b7@t450s.home \
--to=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=van.freenix@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®