From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: ankita@nvidia.com, yishaih@nvidia.com,
shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
aniketa@nvidia.com, cjia@nvidia.com, kwankhede@nvidia.com,
targupta@nvidia.com, vsethi@nvidia.com, acurrid@nvidia.com,
apopple@nvidia.com, jhubbard@nvidia.com, danw@nvidia.com,
anuaggarwal@nvidia.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v8 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper
Date: Thu, 7 Sep 2023 21:34:41 -0300 [thread overview]
Message-ID: <ZPpsIU3vAcfFh2e6@nvidia.com> (raw)
In-Reply-To: <20230907135546.70239f1b.alex.williamson@redhat.com>
On Thu, Sep 07, 2023 at 01:55:46PM -0600, Alex Williamson wrote:
> There's perhaps an argument whether userspace should compose this
> device itself, for example finding the firmware attributes in sysfs and
> directly mmap'ing the coherent memory via /dev/mem to back a virtual
> BAR or otherwise pass-through this associated region.
I don't think this works, secure boot turns off /dev/mem and other
things that would let you do this AFAIK.
> I've previously raised the point whether the coherent region here
> might be exposed as a device specific region (such as we do for the
> above IGD regions) rather than a virtual BAR, but the NVIDIA folks feel
> strongly that the BAR approach is correct.
I think it really depends on what the qemu side wants to do..
> Please continue the discussion, but I'm not seeing anything here that
> feels significantly different than what we created vfio-pci variant
> drivers to do.
Right, the driver seems fine for what the infrastructure was created
to do.
Jason
next prev parent reply other threads:[~2023-09-08 0:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 12:41 [PATCH v8 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper ankita
2023-09-07 19:55 ` Alex Williamson
2023-09-08 0:34 ` Jason Gunthorpe [this message]
2023-09-08 4:04 ` Alex Williamson
2023-09-08 8:50 ` Christoph Hellwig
2023-09-08 12:15 ` Jason Gunthorpe
2023-09-11 7:12 ` Tian, Kevin
2023-09-11 8:17 ` Ankit Agrawal
2023-09-11 8:24 ` Tian, Kevin
2023-09-11 9:19 ` 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=ZPpsIU3vAcfFh2e6@nvidia.com \
--to=jgg@nvidia.com \
--cc=acurrid@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=anuaggarwal@nvidia.com \
--cc=apopple@nvidia.com \
--cc=cjia@nvidia.com \
--cc=danw@nvidia.com \
--cc=hch@infradead.org \
--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.