From: anup.patel@broadcom.com (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] iommu: Add capability IOMMU_CAP_BYPASS
Date: Wed, 19 Jul 2017 16:49:00 +0530 [thread overview]
Message-ID: <CAALAos_o25mtphxcVE0rr9dE8YAm-os2C_HD9oDnt41ZMDP8pA@mail.gmail.com> (raw)
In-Reply-To: <675744d3-b070-1245-6ebc-579c4b5f4a75@arm.com>
On Wed, Jul 19, 2017 at 4:28 PM, Robin Murphy <robin.murphy@arm.com> wrote:
> On 19/07/17 10:33, Anup Patel wrote:
>> Some of the IOMMUs (such as ARM SMMU) are capable of bypassing
>> transactions for which no IOMMU domain is configured.
>>
>> This patch adds IOMMU_CAP_BYPASS which can be used by IOMMU
>> drivers to advertise transation bypass capability of an IOMMU.
>
> Whatever the intended semantics of this are, I can't help thinking it
> would be better served by allowing callers to explicitly allocate their
> own IOMMU_DOMAIN_IDENTITY domains. That would also be useful for the
> problem we have with legacy virtio devices behind real IOMMUs.
We want to use VFIO no-IOMMU mode for FlexRM device but
currently it does not allow on our SOC because IOMMU ops are
registered for platform bus.
Regards,
Anup
next prev parent reply other threads:[~2017-07-19 11:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 9:33 [PATCH 0/5] FlexRM support in VFIO platform Anup Patel
2017-07-19 9:33 ` [PATCH 1/5] iommu: Add capability IOMMU_CAP_BYPASS Anup Patel
2017-07-19 10:58 ` Robin Murphy
2017-07-19 11:19 ` Anup Patel [this message]
2017-07-19 11:23 ` Will Deacon
2017-07-19 11:26 ` Anup Patel
2017-07-19 11:29 ` Robin Murphy
2017-07-19 11:30 ` Will Deacon
2017-07-19 11:33 ` Anup Patel
2017-07-19 9:33 ` [PATCH 2/5] iommu/arm-smmu: add IOMMU_CAP_BYPASS to the ARM SMMU driver Anup Patel
2017-07-19 10:59 ` Robin Murphy
2017-07-19 9:33 ` [PATCH 3/5] iommu/arm-smmu-v3: add IOMMU_CAP_BYPASS to the ARM SMMUv3 driver Anup Patel
2017-07-19 11:00 ` Robin Murphy
2017-07-19 11:23 ` Anup Patel
2017-07-19 11:25 ` Will Deacon
2017-07-19 11:31 ` Anup Patel
2017-07-19 11:33 ` Will Deacon
2017-07-19 11:39 ` Anup Patel
2017-07-19 11:53 ` Will Deacon
2017-07-20 4:02 ` Anup Patel
2017-07-20 9:10 ` Will Deacon
2017-07-20 11:08 ` Anup Patel
2017-07-20 11:17 ` Will Deacon
2017-07-20 11:17 ` Robin Murphy
2017-07-24 17:16 ` Alex Williamson
2017-07-24 17:23 ` Robin Murphy
2017-07-24 19:06 ` Alex Williamson
2017-07-25 8:59 ` Anup Patel
2017-07-19 9:33 ` [PATCH 4/5] vfio: Allow No-IOMMU mode for IOMMUs with bypass capability Anup Patel
2017-07-19 9:33 ` [PATCH 5/5] vfio: platform: reset: Add Broadcom FlexRM reset module Anup Patel
2017-07-19 16:50 ` Scott Branden
2017-07-20 4:05 ` Anup Patel
2017-07-19 10:57 ` [PATCH 0/5] FlexRM support in VFIO platform Robin Murphy
2017-07-19 11:17 ` Anup Patel
2017-07-19 11:25 ` Robin Murphy
2017-07-19 11:28 ` 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=CAALAos_o25mtphxcVE0rr9dE8YAm-os2C_HD9oDnt41ZMDP8pA@mail.gmail.com \
--to=anup.patel@broadcom.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).