mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donald Dutile <ddutile@redhat.com>
To: Alex Williamson <alex@shazbot.org>, ankita@nvidia.com
Cc: jgg@ziepe.ca, yishaih@nvidia.com, skolothumtho@nvidia.com,
	kevin.tian@intel.com, aniketa@nvidia.com, vsethi@nvidia.com,
	mochs@nvidia.com, Yunxiang.Li@amd.com, yi.l.liu@intel.com,
	zhangdongdong@eswincomputing.com, avihaih@nvidia.com,
	bhelgaas@google.com, peterx@redhat.com, pstanner@redhat.com,
	apopple@nvidia.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, cjia@nvidia.com,
	kwankhede@nvidia.com, targupta@nvidia.com, zhiw@nvidia.com,
	danw@nvidia.com, dnigam@nvidia.com, kjaju@nvidia.com
Subject: Re: [PATCH v3 5/7] vfio: move barmap to a separate function and export
Date: Fri, 21 Nov 2025 15:58:19 -0500	[thread overview]
Message-ID: <9b25494c-0271-4469-a7f4-71876eadd4e3@redhat.com> (raw)
In-Reply-To: <20251121093949.54f647a6.alex@shazbot.org>

On 11/21/25 11:39 AM, Alex Williamson wrote:
> On Fri, 21 Nov 2025 14:11:39 +0000
> <ankita@nvidia.com> wrote:
> 
>> From: Ankit Agrawal <ankita@nvidia.com>
>>
>> Move the code to map the BAR to a separate function.
>>
>> This would be reused by the nvgrace-gpu module.
>>
>> Signed-off-by: Ankit Agrawal <ankita@nvidia.com>
>> ---
>>   drivers/vfio/pci/vfio_pci_core.c | 38 ++++++++++++++++++++++----------
>>   include/linux/vfio_pci_core.h    |  1 +
>>   2 files changed, 27 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
>> index 29dcf78905a6..d1ff1c0aa727 100644
>> --- a/drivers/vfio/pci/vfio_pci_core.c
>> +++ b/drivers/vfio/pci/vfio_pci_core.c
>> @@ -1717,6 +1717,29 @@ static const struct vm_operations_struct vfio_pci_mmap_ops = {
>>   #endif
>>   };
>>   
>> +int vfio_pci_core_barmap(struct vfio_pci_core_device *vdev, unsigned int index)
>> +{
>> +	struct pci_dev *pdev = vdev->pdev;
>> +	int ret;
>> +
>> +	if (vdev->barmap[index])
>> +		return 0;
>> +
>> +	ret = pci_request_selected_regions(pdev,
>> +					   1 << index, "vfio-pci");
>> +	if (ret)
>> +		return ret;
>> +
>> +	vdev->barmap[index] = pci_iomap(pdev, index, 0);
>> +	if (!vdev->barmap[index]) {
>> +		pci_release_selected_regions(pdev, 1 << index);
>> +		return -ENOMEM;
>> +	}
>> +
>> +	return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(vfio_pci_core_barmap);
> 
> Looks a lot like vfio_pci_core_setup_barmap() ;)
> 
> Thanks,
> Alex
> 
+1 ... and below ...
> 
>> +
>>   int vfio_pci_core_mmap(struct vfio_device *core_vdev, struct vm_area_struct *vma)
>>   {
>>   	struct vfio_pci_core_device *vdev =
>> @@ -1761,18 +1784,9 @@ int vfio_pci_core_mmap(struct vfio_device *core_vdev, struct vm_area_struct *vma
>>   	 * Even though we don't make use of the barmap for the mmap,
>>   	 * we need to request the region and the barmap tracks that.
>>   	 */
>> -	if (!vdev->barmap[index]) {
>> -		ret = pci_request_selected_regions(pdev,
>> -						   1 << index, "vfio-pci");
>> -		if (ret)
>> -			return ret;
>> -
>> -		vdev->barmap[index] = pci_iomap(pdev, index, 0);
>> -		if (!vdev->barmap[index]) {
>> -			pci_release_selected_regions(pdev, 1 << index);
>> -			return -ENOMEM;
>> -		}
>> -	}
>> +	ret = vfio_pci_core_barmap(vdev, index);
>> +	if (ret)
>> +		return ret;
>>   
so, vfio_pci_core_mmap() should be calling vfio_pci_core_setup_barmap() vs. what it does above currently?

--Don

>>   	vma->vm_private_data = vdev;
>>   	vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
>> diff --git a/include/linux/vfio_pci_core.h b/include/linux/vfio_pci_core.h
>> index a097a66485b4..75f04d613e0c 100644
>> --- a/include/linux/vfio_pci_core.h
>> +++ b/include/linux/vfio_pci_core.h
>> @@ -121,6 +121,7 @@ ssize_t vfio_pci_core_write(struct vfio_device *core_vdev, const char __user *bu
>>   		size_t count, loff_t *ppos);
>>   vm_fault_t vfio_pci_map_pfn(struct vm_fault *vmf, unsigned long pfn,
>>   			    unsigned int order);
>> +int vfio_pci_core_barmap(struct vfio_pci_core_device *vdev, unsigned int index);
>>   int vfio_pci_core_mmap(struct vfio_device *core_vdev, struct vm_area_struct *vma);
>>   void vfio_pci_core_request(struct vfio_device *core_vdev, unsigned int count);
>>   int vfio_pci_core_match(struct vfio_device *core_vdev, char *buf);
> 
> 


  reply	other threads:[~2025-11-21 20:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 14:11 [PATCH v3 0/7] vfio/nvgrace-gpu: Support huge PFNMAP and wait for GPU ready post reset ankita
2025-11-21 14:11 ` [PATCH v3 1/7] vfio/nvgrace-gpu: Use faults to map device memory ankita
2025-11-21 14:11 ` [PATCH v3 2/7] vfio: export function to map the VMA ankita
2025-11-21 14:11 ` [PATCH v3 3/7] vfio/nvgrace-gpu: Add support for huge pfnmap ankita
2025-11-21 14:11 ` [PATCH v3 4/7] vfio: export vfio_find_cap_start ankita
2025-11-21 14:11 ` [PATCH v3 5/7] vfio: move barmap to a separate function and export ankita
2025-11-21 16:39   ` Alex Williamson
2025-11-21 20:58     ` Donald Dutile [this message]
2025-11-21 21:08       ` Alex Williamson
2025-11-21 14:11 ` [PATCH v3 6/7] vfio/nvgrace-gpu: split the code to wait for GPU ready ankita
2025-11-21 14:11 ` [PATCH v3 7/7] vfio/nvgrace-gpu: wait for the GPU mem to be ready ankita
2025-11-21 16:59   ` Alex Williamson

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=9b25494c-0271-4469-a7f4-71876eadd4e3@redhat.com \
    --to=ddutile@redhat.com \
    --cc=Yunxiang.Li@amd.com \
    --cc=alex@shazbot.org \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=apopple@nvidia.com \
    --cc=avihaih@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=cjia@nvidia.com \
    --cc=danw@nvidia.com \
    --cc=dnigam@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kjaju@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochs@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=pstanner@redhat.com \
    --cc=skolothumtho@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --cc=yishaih@nvidia.com \
    --cc=zhangdongdong@eswincomputing.com \
    --cc=zhiw@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®