From: alex.williamson@redhat.com (Alex Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] vfio: Allow No-IOMMU mode without checking iommu_present()
Date: Mon, 24 Jul 2017 11:24:06 -0600 [thread overview]
Message-ID: <20170724112406.42b69c8b@w520.home> (raw)
In-Reply-To: <1500525154-5200-2-git-send-email-anup.patel@broadcom.com>
On Thu, 20 Jul 2017 10:02:33 +0530
Anup Patel <anup.patel@broadcom.com> wrote:
> Not allowing No-IOMMU mode for devices already having
> iommu_ops on their bus is very conservative.
>
> We now have IOMMU (such as ARM SMMU) which can bypass
> transcations when IOMMU is not configured for a given
> device. In addition, it is not necessary to have all
> devices on bus to be upstream to an IOMMU on that bus.
>
> Due above reasons, having iommu_present() check for
> VFIO No-IOMMU mode is not appropriate.
>
> Signed-off-by: Anup Patel <anup.patel@broadcom.com>
> ---
> drivers/vfio/vfio.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index 330d505..9d90de7 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -124,11 +124,10 @@ struct iommu_group *vfio_iommu_group_get(struct device *dev)
> #ifdef CONFIG_VFIO_NOIOMMU
> /*
> * With noiommu enabled, an IOMMU group will be created for a device
> - * that doesn't already have one and doesn't have an iommu_ops on their
> - * bus. We set iommudata simply to be able to identify these groups
> - * as special use and for reclamation later.
> + * that doesn't already have one. We set iommudata simply to be able
> + * to identify these groups as special use and for reclamation later.
> */
> - if (group || !noiommu || iommu_present(dev->bus))
> + if (group || !noiommu)
> return group;
>
> group = iommu_group_alloc();
Nak, no-iommu is intentionally conservative. How do we tell the
difference between the iommu_ops available to us with a fake group vs
a proper group created by the iommu if we ignore iommu_present()? If
an iommu exists, use it. Thanks,
Alex
next prev parent reply other threads:[~2017-07-24 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 4:32 [PATCH v2 0/2] FlexRM support in VFIO platform Anup Patel
2017-07-20 4:32 ` [PATCH v2 1/2] vfio: Allow No-IOMMU mode without checking iommu_present() Anup Patel
2017-07-20 9:19 ` Will Deacon
2017-07-24 17:24 ` Alex Williamson [this message]
2017-07-20 4:32 ` [PATCH v2 2/2] vfio: platform: reset: Add Broadcom FlexRM reset module Anup Patel
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=20170724112406.42b69c8b@w520.home \
--to=alex.williamson@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).