mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Farhan Ali <alifm@linux.ibm.com>
To: Alex Williamson <alex@shazbot.org>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	kvm@vger.kernel.org, borntraeger@linux.ibm.com, mattev@meta.com,
	schnelle@linux.ibm.com
Subject: Re: [PATCH v1] vfio/pci: Avoid mapping BARs for devices with non-mappable BARs
Date: Wed, 29 Jul 2026 14:32:45 -0700	[thread overview]
Message-ID: <42a3b06d-ecaa-4339-9472-7c592694f877@linux.ibm.com> (raw)
In-Reply-To: <20260729143603.175f60a7@shazbot.org>


On 7/29/2026 1:36 PM, Alex Williamson wrote:
> On Wed, 29 Jul 2026 13:28:46 -0700
> Farhan Ali <alifm@linux.ibm.com> wrote:
>
>> On 7/29/2026 12:41 PM, Matthew Rosato wrote:
>>> On 7/29/26 2:11 PM, Farhan Ali wrote:
>>>> vfio_pci_core_map_bars() calls pci_iomap() to set up BAR resources, but not
>>>> all devices support having their BARs mapped by the CPU. The
>>>> non_mappable_bars flag indicates that a PCI device's BARs cannot be
>>>> accessed by the CPU. The ISM device on s390 is one such device. The BAR
>>>> size for an ISM device is 256 TiB, and attempting to map the BAR will lead
>>>> to warnings:
>>>>
>>>> vmalloc_node_range for size 281474976714752 failed: Address range
>>>> restricted to 0x2110bab00000 - 0x21903ab00000
>>>>
>>>> Use pdev->non_mappable_bars to skip pci_iomap() for such devices. This flag
>>>> is set by the PCI core at enumeration time and already serves the same
>>>> purpose in vfio_pci_probe_mmaps().
>>>>
>>>> Fixes: 05f2a68b407a ("vfio/pci: Set up BAR resources and maps in vfio_pci_core_enable()")
>>>> Reported-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>>>> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
>>>> ---
>>>>    drivers/vfio/pci/vfio_pci_core.c | 3 +++
>>>>    1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
>>>> index 3f11a9624b9c..6a184588ff23 100644
>>>> --- a/drivers/vfio/pci/vfio_pci_core.c
>>>> +++ b/drivers/vfio/pci/vfio_pci_core.c
>>>> @@ -554,6 +554,9 @@ static void vfio_pci_core_map_bars(struct vfio_pci_core_device *vdev)
>>>>    
>>>>    		vdev->barmap[bar] = IOMEM_ERR_PTR(-ENODEV);
>>>>    
>>>> +		if (pdev->non_mappable_bars)
>>>> +			continue;
>>>> +
>>> This would work for the ISM case at least, but I wonder: should we check
>>> vdev->bar_mmap_supported[bar] instead?
>>>
>>> My question boils down to: do we still want messages for some of the
>>> cases where we set vdev->bar_mmap_supported[bar] = false in
>>> vfio_pci_probe_mmaps()?
>> AFAIU vfio_pci_probe_mmaps() is only called in
>> vfio_pci_core_finish_enable(). Since vfio_pci_core_map_bars() is called
>> in vfio_pci_core_enable(), and before vfio_pci_core_finish_enable(),
>> bar_mmap_supported would be false here for all devices. So I don't think
>> it would work here, unless I missed something?
> Also IO Port and sub-page MMIO BARs are things that do exist.  Thanks,
>
> Alex

Just to clarify, are you suggesting we expand this check to also avoid 
mapping IO port and sub-page MMIO BARs?

Thanks

Farhan



  reply	other threads:[~2026-07-29 21:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 18:11 Farhan Ali
2026-07-29 19:41 ` Matthew Rosato
2026-07-29 20:28   ` Farhan Ali
2026-07-29 20:36     ` Alex Williamson
2026-07-29 21:32       ` Farhan Ali [this message]
2026-07-29 21:50         ` Alex Williamson
2026-08-03 16:39           ` Farhan Ali
2026-08-03 19:54             ` Alex Williamson
2026-08-03 20:44               ` Farhan Ali
2026-08-04 13:39                 ` Matthew Rosato
2026-08-10 17:43                   ` Farhan Ali
2026-08-04 14:09 ` Niklas Schnelle
2026-08-10 23:40 ` 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=42a3b06d-ecaa-4339-9472-7c592694f877@linux.ibm.com \
    --to=alifm@linux.ibm.com \
    --cc=alex@shazbot.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mattev@meta.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=schnelle@linux.ibm.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®