From: Jason Gunthorpe <jgg@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] vfio: Depend on MMU
Date: Mon, 8 Mar 2021 14:23:13 -0400 [thread overview]
Message-ID: <20210308182313.GA4247@nvidia.com> (raw)
In-Reply-To: <20210308191421.7f823b28.cohuck@redhat.com>
On Mon, Mar 08, 2021 at 07:14:21PM +0100, Cornelia Huck wrote:
> On Fri, 5 Mar 2021 19:11:41 -0400
> Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > On Fri, Mar 05, 2021 at 09:46:49AM +0100, Cornelia Huck wrote:
> > > On Thu, 4 Mar 2021 21:30:03 -0400
> > > Jason Gunthorpe <jgg@nvidia.com> wrote:
> > >
> > > > VFIO_IOMMU_TYPE1 does not compile with !MMU:
> > > >
> > > > ../drivers/vfio/vfio_iommu_type1.c: In function 'follow_fault_pfn':
> > > > ../drivers/vfio/vfio_iommu_type1.c:536:22: error: implicit declaration of function 'pte_write'; did you mean 'vfs_write'? [-Werror=implicit-function-declaration]
> > > >
> > > > So require it.
> > > >
> > > > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > > > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > > > drivers/vfio/Kconfig | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig
> > > > index 90c0525b1e0cf4..67d0bf4efa1606 100644
> > > > +++ b/drivers/vfio/Kconfig
> > > > @@ -22,7 +22,7 @@ config VFIO_VIRQFD
> > > > menuconfig VFIO
> > > > tristate "VFIO Non-Privileged userspace driver framework"
> > > > select IOMMU_API
> > > > - select VFIO_IOMMU_TYPE1 if (X86 || S390 || ARM || ARM64)
> > > > + select VFIO_IOMMU_TYPE1 if MMU && (X86 || S390 || ARM || ARM64)
> > > > help
> > > > VFIO provides a framework for secure userspace device drivers.
> > > > See Documentation/driver-api/vfio.rst for more details.
> > >
> > > Actually, I'm wondering how much sense vfio makes on !MMU at all? (And
> > > maybe just merge this with your patch that switches IOMMU_API from a
> > > depend to a select, because that is the change that makes the MMU
> > > dependency required?)
> >
> > Why does changing depend to select affect MMU vs !MMU? Am I missing
> > something?
> >
> > It looks like IOMMU_API can be turned with ARM !MMU here, for
> > instance:
> >
> > config MSM_IOMMU
> > bool "MSM IOMMU Support"
> > depends on ARM
> > depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
> > select IOMMU_API
>
> But that one is sitting under a menu depending on MMU, isn't it?
Yep.
Still, I'd keep the two ideas as two patches - order this one first.
Jason
next prev parent reply other threads:[~2021-03-08 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 1:30 [PATCH] vfio: Depend on MMU Jason Gunthorpe
2021-03-05 8:46 ` Cornelia Huck
2021-03-05 23:11 ` Jason Gunthorpe
2021-03-08 18:14 ` Cornelia Huck
2021-03-08 18:23 ` Jason Gunthorpe [this message]
2021-03-08 17:59 ` Alex Williamson
2021-03-08 18:12 ` Cornelia Huck
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=20210308182313.GA4247@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.