From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Leon Romanovsky" <leon@kernel.org>,
"Leon Romanovsky" <leonro@nvidia.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
"Christoph Hellwig" <hch@lst.de>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
"Jens Axboe" <axboe@kernel.dk>, "Joerg Roedel" <joro@8bytes.org>,
kvm@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
linux-pci@vger.kernel.org,
"Logan Gunthorpe" <logang@deltatee.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH v1 04/10] PCI/P2PDMA: Refactor to separate core P2P functionality from memory allocation
Date: Wed, 6 Aug 2025 21:02:07 -0300 [thread overview]
Message-ID: <20250807000207.GE184255@nvidia.com> (raw)
In-Reply-To: <20250806154214.1c2618e8.alex.williamson@redhat.com>
On Wed, Aug 06, 2025 at 03:42:14PM -0600, Alex Williamson wrote:
> > + p2p->mem.owner = &pdev->dev;
> > + /* On all p2p platforms bus_offset is the same for all BARs */
> > + p2p->mem.bus_offset =
> > + pci_bus_address(pdev, 0) - pci_resource_start(pdev, 0);
>
> But not all devices implement BAR0, nor is BAR0 necessarily in the
> memory space, wouldn't this calculation be wrong if BAR0 were
> unimplemented or an IO BAR?
I think you are correct about this.
> Even within memory BARs I can imagine different translations for 32
> vs 64 bit, prefetch vs non-prefetch, but per the comment I guess
> we're excluding those. Thanks,
Humm, I had thought it was consistent for the device, but I guess not:
resource_list_for_each_entry(window, &bridge->windows) {
if (resource_contains(window->res, res)) {
offset = window->offset;
Seems like each window can have its own offset.
So the p2p should be made per-bar, and hold the bar index from the
constructor..
Jason
next prev parent reply other threads:[~2025-08-07 0:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 13:00 [PATCH v1 00/10] vfio/pci: Allow MMIO regions to be exported through dma-buf Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 01/10] PCI/P2PDMA: Remove redundant bus_offset from map state Leon Romanovsky
2025-08-06 20:58 ` Alex Williamson
2025-09-02 11:06 ` Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 02/10] PCI/P2PDMA: Separate the mmap() support from the core logic Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 03/10] PCI/P2PDMA: Simplify bus address mapping API Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 04/10] PCI/P2PDMA: Refactor to separate core P2P functionality from memory allocation Leon Romanovsky
2025-08-06 21:42 ` Alex Williamson
2025-08-07 0:02 ` Jason Gunthorpe [this message]
2025-08-04 13:00 ` [PATCH v1 05/10] PCI/P2PDMA: Export pci_p2pdma_map_type() function Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 06/10] types: move phys_vec definition to common header Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 07/10] vfio: Export vfio device get and put registration helpers Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 08/10] vfio/pci: Enable peer-to-peer DMA transactions by default Leon Romanovsky
2025-08-06 22:02 ` Alex Williamson
2025-09-02 12:58 ` Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 09/10] vfio/pci: Share the core device pointer while invoking feature functions Leon Romanovsky
2025-08-04 13:00 ` [PATCH v1 10/10] vfio/pci: Add dma-buf export support for MMIO regions Leon Romanovsky
2025-08-04 15:26 ` Leon Romanovsky
2025-08-06 22:24 ` Alex Williamson
2025-08-04 14:10 ` [PATCH v1 00/10] vfio/pci: Allow MMIO regions to be exported through dma-buf Benjamin LaHaise
2025-08-04 14:18 ` Leon Romanovsky
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=20250807000207.GE184255@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=vivek.kasireddy@intel.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).