From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Ankit Agrawal <ankita@nvidia.com>,
Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
Vikram Sethi <vsethi@nvidia.com>,
Andy Currid <acurrid@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Dan Williams <danw@nvidia.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper
Date: Fri, 28 Jul 2023 09:21:44 -0600 [thread overview]
Message-ID: <20230728092144.5f51343f.alex.williamson@redhat.com> (raw)
In-Reply-To: <ZMO1H/uepDTtAaet@nvidia.com>
On Fri, 28 Jul 2023 09:31:27 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Fri, Jul 28, 2023 at 04:36:05AM +0000, Ankit Agrawal wrote:
> >
> > >> +static ssize_t nvgrace_gpu_vfio_pci_read(struct vfio_device *core_vdev,
> > >> + char __user *buf, size_t count, loff_t *ppos)
> > >> +{
> > >> + unsigned int index = VFIO_PCI_OFFSET_TO_INDEX(*ppos);
> > >> + struct nvgrace_gpu_vfio_pci_core_device *nvdev = container_of(
> > >> + core_vdev, struct nvgrace_gpu_vfio_pci_core_device, core_device.vdev);
> > >> + u64 offset = *ppos & VFIO_PCI_OFFSET_MASK;
> > >> + u8 val = 0xFF;
> > >> + size_t i;
> > >> +
> > >> + /*
> > >> + * Only the device memory present on the hardware is mapped, which may
> > >> + * not be power-of-2 aligned. A read to the BAR2 region implies an
> > >> + * access outside the available device memory on the hardware.
> > >> + */
> > >
> > > This is not true, userspace has no requirement to only access BAR2 via
> > > mmap. This should support reads from within the coherent memory area.
> >
> > Just to confirm, the ask is to just update the comment to reflect the behavior,
> > right? (I missed to do that in this posting). Because we do redirect the call to
> > vfio_pci_core_read() here which will perform the read that is within the device
> > region. The read response to synthesize -1 is only for the range that is outside
> > the device memory region.
>
> This doesn't seem right, vfio_pci_core_read() will use pci_iomap() to
> get a mapping which will be a DEVICE mapping, this will make the
> access incoherent with any cachable mappings.
Right, but also vfio_pci_core_read() doesn't know anything about this
virtual BAR2, so any in-range BAR2 accesses will error the same as
trying to access an unimplemented BAR. It's not just the comment,
there's no code here to handle a read(2) from in-bound BAR2 accesses.
Thanks,
Alex
next prev parent reply other threads:[~2023-07-28 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 17:43 ankita
2023-07-27 20:29 ` Alex Williamson
2023-07-28 4:36 ` Ankit Agrawal
2023-07-28 12:31 ` Jason Gunthorpe
2023-07-28 15:21 ` Alex Williamson [this message]
2023-07-31 14:32 ` Ankit Agrawal
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=20230728092144.5f51343f.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=acurrid@nvidia.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=cjia@nvidia.com \
--cc=danw@nvidia.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=targupta@nvidia.com \
--cc=vsethi@nvidia.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®