linux-kernel - Re: [PATCH v8 09/18] vfio/platform: support MMAP of MMIO regions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1413996975.4202.226.camel@ul30vt.home>
Date:	Wed, 22 Oct 2014 10:56:15 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Antonios Motakis <a.motakis@...tualopensystems.com>
Cc:	kvm-arm <kvmarm@...ts.cs.columbia.edu>,
	Linux IOMMU <iommu@...ts.linux-foundation.org>,
	Will Deacon <will.deacon@....com>,
	VirtualOpenSystems Technical Team <tech@...tualopensystems.com>,
	Christoffer Dall <christoffer.dall@...aro.org>,
	Eric Auger <eric.auger@...aro.org>,
	Kim Phillips <kim.phillips@...escale.com>,
	Marc Zyngier <marc.zyngier@....com>,
	"open list:VFIO DRIVER" <kvm@...r.kernel.org>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 09/18] vfio/platform: support MMAP of MMIO regions

On Wed, 2014-10-22 at 15:55 +0200, Antonios Motakis wrote:
> On Tue, Oct 21, 2014 at 6:51 PM, Alex Williamson
> <alex.williamson@...hat.com> wrote:
> > On Mon, 2014-10-13 at 15:10 +0200, Antonios Motakis wrote:
> >> Allow to memory map the MMIO regions of the device so userspace can
> >> directly access them. PIO regions are not being handled at this point.
> >>
> >> Signed-off-by: Antonios Motakis <a.motakis@...tualopensystems.com>
> >> ---
> >>  drivers/vfio/platform/vfio_platform_common.c | 57 ++++++++++++++++++++++++++++
> >>  1 file changed, 57 insertions(+)
> >>
> >> diff --git a/drivers/vfio/platform/vfio_platform_common.c b/drivers/vfio/platform/vfio_platform_common.c
> >> index ac74710..4db7187 100644
> >> --- a/drivers/vfio/platform/vfio_platform_common.c
> >> +++ b/drivers/vfio/platform/vfio_platform_common.c
> >> @@ -57,6 +57,16 @@ static int vfio_platform_regions_init(struct vfio_platform_device *vdev)
> >>                       if (!(res->flags & IORESOURCE_READONLY))
> >>                               vdev->regions[i].flags |=
> >>                                       VFIO_REGION_INFO_FLAG_WRITE;
> >> +
> >> +                     /*
> >> +                      * Only regions addressed with PAGE granularity may be
> >> +                      * MMAPed securely.
> >> +                      */
> >> +                     if (!(vdev->regions[i].addr & ~PAGE_MASK) &&
> >> +                                     !(vdev->regions[i].size & ~PAGE_MASK))
> >> +                             vdev->regions[i].flags |=
> >> +                                     VFIO_REGION_INFO_FLAG_MMAP;
> >> +
> >
> > Should this be included in the above !readonly test?  I don't see that
> > we're doing anything below that would prevent writes to the mmap for a
> > readonly resource.  I suspect that just like PCI, it's not all that
> > useful to provide mmap support for read-only regions.  They're not
> > typically performance paths.
> 
> Indeed. Alternatively we could just MMAP the region as read only as
> well. Even if typically they are not performance critical areas, maybe
> it doesn't hurt to allow MMAP when possible.

Sure, we could allow a read-only mmap.  On PCI the only read-only region
is the PCI option ROM.  The PCI spec indicates that devices may use the
same address decoders for the ROM as for BARs, so the ROM and BAR may
not be simultaneously accessible.  QEMU also caches the ROM once the
guest does read it, so it's never been an issue to allow mmap of that
resource.  I would probably only bother to provide read-only mmap if you
know vfio-platform devices are going to make more significant use of
read-only regions.  Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/