From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Ankit Agrawal <ankita@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
"shameerali.kolothum.thodi@huawei.com"
<shameerali.kolothum.thodi@huawei.com>,
"kevin.tian@intel.com" <kevin.tian@intel.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 v7 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper
Date: Wed, 23 Aug 2023 09:24:29 -0600 [thread overview]
Message-ID: <20230823092429.643b4f7b.alex.williamson@redhat.com> (raw)
In-Reply-To: <ZOYix7kFDYcvZ/gp@nvidia.com>
On Wed, 23 Aug 2023 12:16:23 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Wed, Aug 23, 2023 at 09:14:07AM -0600, Alex Williamson wrote:
> > On Wed, 23 Aug 2023 14:50:31 +0000
> > Ankit Agrawal <ankita@nvidia.com> wrote:
> >
> > > >> + if (index == VFIO_PCI_BAR2_REGION_INDEX) {
> > > >> + if (!nvdev->opregion) {
> > > >> + nvdev->opregion = memremap(nvdev->hpa, nvdev->mem_length, MEMREMAP_WB);
> > > >> + if (!nvdev->opregion)
> > > >> + return -ENOMEM;
> > > >> + }
> > > >
> > > > [AW] Seems like this would be susceptible to concurrent accesses causing
> > > > duplicate mappings.
> > > >
> > > > [JG] Needs some kind of locking on opregion
> > >
> > > Right, will add a new lock item in nvdev to control the access to opregion/memmap.
> > > Please let me know if it is preferable to do memremap in open_device instead of
> > > read/write.
> >
> > That's a valid option also, certainly avoids the locking and
> > serialization per access. Thanks,
>
> open_device is no good, that would waste large amounts of kernel
> memory for page tables to support something we don't expect to be
> used.
A lock it is then, I guess this is a very large range of memory. The
contention/serialization is also not a priority, we expect access
through the mmap for anything other than debug. Thanks,
Alex
next prev parent reply other threads:[~2023-08-23 15:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 20:23 [PATCH v7 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper ankita
2023-08-22 22:29 ` Alex Williamson
2023-08-23 13:56 ` Jason Gunthorpe
2023-08-23 14:18 ` Ankit Agrawal
2023-08-23 14:25 ` Jason Gunthorpe
2023-08-23 14:26 ` Alex Williamson
2023-08-23 14:50 ` Ankit Agrawal
2023-08-23 15:14 ` Alex Williamson
2023-08-23 15:16 ` Jason Gunthorpe
2023-08-23 15:24 ` Alex Williamson [this message]
2023-08-30 13:50 ` Christoph Hellwig
2023-08-30 15:39 ` Jason Gunthorpe
2023-08-30 15:39 ` Jason Gunthorpe
2023-08-31 12:26 ` Christoph Hellwig
2023-08-31 13:51 ` Ankit Agrawal
2023-08-31 13:51 ` Ankit Agrawal
2023-08-31 14:04 ` Christoph Hellwig
2023-08-31 18:21 ` Alex Williamson
2023-08-31 18:21 ` Alex Williamson
2023-09-01 0:44 ` Jason Gunthorpe
2023-09-01 0:44 ` Jason Gunthorpe
2023-09-01 5:48 ` Christoph Hellwig
2023-09-01 5:47 ` Christoph Hellwig
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=20230823092429.643b4f7b.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=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=targupta@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=yishaih@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 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.