From: Alex Williamson <alex.williamson@redhat.com>
To: Eric Auger <eric.auger@linaro.org>
Cc: a.motakis@virtualopensystems.com, kvmarm@lists.cs.columbia.edu,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, tech@virtualopensystems.com,
a.rigo@virtualopensystems.com, B08248@freescale.com,
kim.phillips@linaro.org, jan.kiszka@siemens.com,
kvm@vger.kernel.org, R65777@freescale.com, B07421@freescale.com,
christoffer.dall@linaro.org, agraf@suse.de, B16395@freescale.com,
will.deacon@arm.com
Subject: Re: [RFC PATCH v4 06/10] VFIO_PLATFORM: Read and write support for the device fd
Date: Tue, 25 Mar 2014 12:56:33 -0600 [thread overview]
Message-ID: <1395773793.632.152.camel@ul30vt.home> (raw)
In-Reply-To: <5331B22C.6090100@linaro.org>
On Tue, 2014-03-25 at 17:43 +0100, Eric Auger wrote:
> > Date: Sat, 8 Feb 2014 18:29:36 +0100
> > VFIO returns a file descriptor which we can use to manipulate the memory
> > regions of the device. Since some memory regions we cannot mmap due to
> > security concerns, we also allow to read and write to this file descriptor
> > directly.
> >
> > Signed-off-by: Antonios Motakis <a.motakis@virtualopensystems.com>
> > Tested-by: Alvise Rigo <a.rigo@virtualopensystems.com>
> > ---
> > drivers/vfio/platform/vfio_platform.c | 128 +++++++++++++++++++++++++++++++++-
> > 1 file changed, 125 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/vfio/platform/vfio_platform.c b/drivers/vfio/platform/vfio_platform.c
> > index f7db5c0..ee96078 100644
> > --- a/drivers/vfio/platform/vfio_platform.c
> > +++ b/drivers/vfio/platform/vfio_platform.c
> > @@ -55,7 +55,8 @@ static int vfio_platform_regions_init(struct vfio_platform_device *vdev)
> >
> > region.addr = res->start;
> > region.size = resource_size(res);
> > - region.flags = 0;
> > + region.flags = VFIO_REGION_INFO_FLAG_READ
> > + | VFIO_REGION_INFO_FLAG_WRITE;
> >
> > vdev->region[i] = region;
> > }
> > @@ -150,13 +151,134 @@ static long vfio_platform_ioctl(void *device_data,
> > static ssize_t vfio_platform_read(void *device_data, char __user *buf,
> > size_t count, loff_t *ppos)
> > {
> > - return 0;
> > + struct vfio_platform_device *vdev = device_data;
> > + unsigned int *io;
> > + int i;
> > +
> > + for (i = 0; i < vdev->num_regions; i++) {
> > + struct vfio_platform_region region = vdev->region[i];
> > + unsigned int done = 0;
> > + loff_t off;
> > +
> > + if ((*ppos < region.addr)
> > + || (*ppos + count - 1) >= (region.addr + region.size))
> > + continue;
> > +
> > + io = ioremap_nocache(region.addr, region.size);
> > +
> > + off = *ppos - region.addr;
> > +
> > + while (count) {
> > + size_t filled;
> > +
> > + if (count >= 4 && !(off % 4)) {
> > + u32 val;
> > +
> > + val = ioread32(io + off);
>
> Hi Antonios,
>
> I suspect there is an issue with the read address. Indeed io being an
> unsigned int* the read address is io + off x sizeof (unsigned int) ie.
> io+ offx4 whereas we expect to read io + off. declaring io as a void*
> corrects the issue (or void __iomem *io). Same issue on write.
Yep, the same code for vfio/pci uses void __iomem *io. Thanks,
Alex
next prev parent reply other threads:[~2014-03-25 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140325110619.52107df5d6d0cf0476b33cd4@linaro.org>
2014-03-25 16:43 ` Eric Auger
2014-03-25 18:56 ` Alex Williamson [this message]
2014-02-08 17:29 [RFC PATCH v4 00/10] VFIO support for platform devices Antonios Motakis
2014-02-08 17:29 ` [RFC PATCH v4 06/10] VFIO_PLATFORM: Read and write support for the device fd Antonios Motakis
2014-02-10 22:45 ` Alex Williamson
2014-02-10 23:12 ` Scott Wood
2014-02-10 23:20 ` Alex Williamson
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=1395773793.632.152.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=R65777@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=a.rigo@virtualopensystems.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kim.phillips@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tech@virtualopensystems.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®