From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: ankita@nvidia.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, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, yishaih@nvidia.com,
shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com
Subject: Re: [PATCH v2 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper
Date: Tue, 16 May 2023 21:28:35 -0300 [thread overview]
Message-ID: <ZGQfszAGGKhCp20q@nvidia.com> (raw)
In-Reply-To: <20230516150914.26ae99c3.alex.williamson@redhat.com>
On Tue, May 16, 2023 at 03:09:14PM -0600, Alex Williamson wrote:
> > +# SPDX-License-Identifier: GPL-2.0-only
> > +config NVGPU_VFIO_PCI
> > + tristate "VFIO support for the GPU in the NVIDIA Grace Hopper Superchip"
> > + depends on ARM64 || (COMPILE_TEST && 64BIT)
> > + select VFIO_PCI_CORE
>
> I think this should be a 'depends on' as well, that's what we have for
> the other vfio-pci variant drivers.
It should be removed completely, AFAICT:
config VFIO_PCI
tristate "Generic VFIO support for any PCI device"
select VFIO_PCI_CORE
Ensures it is turned on
if VFIO_PCI
source "drivers/vfio/pci/mlx5/Kconfig"
endif
Autoamtically injects a 'depends on VFIO_PCI' to all the enclosed
kconfig statements (and puts them nicely in the menu)
So we have everything needed already
SELECT is the correct action since it doesn't have a config text.
> Is our test for vm_end < vm_start in vfio-pci-core just paranoia? I
> don't see an equivalent here.
Yes, mm core will not invoke the op with something incorrect.
> Can we also get a comment in the code outlining the various reasons
> that this "BAR" doesn't need the disabled access protections that
> vfio-pci-core implements? For example outlining the behavior relative
> to BAR access while the memory enable bit is disabled, the bus being in
> reset, or the device being in a low-power state.
The HW has some "isolation" feature that kicks in and safely
disconnects the GPU from the CPU.
A lot of work has been done to make things like VFIO and KVM safe
against machine checks/etc under basically all circumstances.
Jason
next prev parent reply other threads:[~2023-05-17 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 4:07 [PATCH v2 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper ankita
2023-05-16 21:09 ` Alex Williamson
2023-05-17 0:28 ` Jason Gunthorpe [this message]
2023-05-25 15:21 ` Alex Williamson
2023-05-29 17:38 ` Jason Gunthorpe
2023-05-17 7:29 ` Tian, Kevin
2023-05-26 5:57 ` Trilok Soni
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=ZGQfszAGGKhCp20q@nvidia.com \
--to=jgg@nvidia.com \
--cc=acurrid@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=cjia@nvidia.com \
--cc=danw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox