mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] vfio/nvgpu: Add vfio pci variant module for grace hopper device
Date: Tue, 25 Apr 2023 10:03:46 -0300	[thread overview]
Message-ID: <ZEfPsm+SVRC/P5T2@ziepe.ca> (raw)
In-Reply-To: <20230420171720.418a3c0d.alex.williamson@redhat.com>

On Thu, Apr 20, 2023 at 05:17:20PM -0600, Alex Williamson wrote:

> > +	/*
> > +	 * Perform a PFN map to the memory. The device BAR1 is backed by the
> > +	 * GPU memory now. Check that the mapping does not overflow out of
> > +	 * the GPU memory size.
> > +	 */
> > +	ret = remap_pfn_range(vma, vma->vm_start, start_pfn + pgoff,
> > +			      min(req_len, nvdev->mem_prop.mem_length - pgoff),
> > +			      vma->vm_page_prot);
> 
> What's the behavior of this "BAR" relative to things like
> PCI_COMMAND_MEMORY or reset?  If the user generates a secondary bus
> reset on the parent bridge in one thread, while accessing the device in
> another thread, isn't that susceptible to platform error handling just
> like any other PCI device?  

This space works more like RAM and it is made cachable as well which
changes how errors are managed compared to PCI.

It doesn't generate any unhandled failures, so we don't need the zap
protection here.

Jason

  reply	other threads:[~2023-04-25 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 22:28 ankita
2023-04-20 23:17 ` Alex Williamson
2023-04-25 13:03   ` Jason Gunthorpe [this message]
2023-05-04  0:41   ` 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=ZEfPsm+SVRC/P5T2@ziepe.ca \
    --to=jgg@nvidia.com \
    --cc=acurrid@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=cjia@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®