mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Anup Patel <anup.patel@broadcom.com>
Cc: Will Deacon <will.deacon@arm.com>, Joerg Roedel <joro@8bytes.org>,
	Baptiste Reynal <b.reynal@virtualopensystems.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Scott Branden <sbranden@broadcom.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
	Linux IOMMU <iommu@lists.linux-foundation.org>,
	kvm@vger.kernel.org,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 0/5] FlexRM support in VFIO platform
Date: Wed, 19 Jul 2017 12:25:44 +0100	[thread overview]
Message-ID: <d4ef45d5-43cc-c632-082d-a92b8681faee@arm.com> (raw)
In-Reply-To: <CAALAos_YTVRu_u8DycSXPgniGru20+fS6wfUskpV5uLRsazcNw@mail.gmail.com>

On 19/07/17 12:17, Anup Patel wrote:
> On Wed, Jul 19, 2017 at 4:27 PM, Robin Murphy <robin.murphy@arm.com> wrote:
>> On 19/07/17 10:33, Anup Patel wrote:
>>> This patchset primarily adds Broadcom FlexRM reset module for
>>> VFIO platform driver. We also have minor improvments in IOMMU
>>> and VFIO driver to allow VFIO no-IOMMU mode access to FlexRM.
>>
>> I'm struggling to understand the IOMMU changes here - what's the
>> FlexRM's hardware relationship with the IOMMU, and how is it different
>> from any other device? Furthermore, if there *is* a relevant IOMMU
>> present, why would no-IOMMU mode need to be involved at all?
> 
> We want to have FlexRM device accessible from user-space
> using VFIO platform with and without IOMMU.
> 
> Currently, if IOMMU ops are available for platform bus then
> I cannot access FlexRM device using VFIO no-IOMMU mode.

So does the FlexRM hardware master through the SMMU or not? If it does,
why do you need no-IOMMU mode? If it doesn't, then that's yet another
reason to fix the real problem, which is the utterly broken notion of
there being 'an IOMMU' on the platform 'bus', rather than papering over
it in VFIO.

Robin.

> Since, SMMU can bypass transactions which do not match
> any SMRs, we should allow no-IOMMU mode for devices
> when IOMMU group is not available.
> 
> Regards,
> Anup
> 

  reply	other threads:[~2017-07-19 11:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19  9:33 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
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 [this message]
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=d4ef45d5-43cc-c632-082d-a92b8681faee@arm.com \
    --to=robin.murphy@arm.com \
    --cc=alex.williamson@redhat.com \
    --cc=anup.patel@broadcom.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=will.deacon@arm.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®