From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>, Alex Williamson <alex@shazbot.org>
Cc: 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: Tue, 4 Aug 2026 09:39:24 -0400 [thread overview]
Message-ID: <e3ac5a11-b37a-48ae-b096-87f0a805cb34@linux.ibm.com> (raw)
In-Reply-To: <a8f2af03-3242-40bf-bf89-e922f0768db3@linux.ibm.com>
>> The bar_mmap_supported flag describes something else, whether the BAR
>> can be mapped into the user address space. My intention was only to
>> point out that there are BARs that cannot be mapped to the user address
>> space because either they're not MMIO or we can't safely map the full
>> page, therefore bar_mmap_supported is an invalid test for whether we
>> should request the region or iomap the BAR.
>>
>> Is there still a gap with the original proposal that I'm missing?
>
> AFAICT this fix should be sufficient. I think Matt's question was to see
> if there were other cases for which bar_mmap_supported were set to
> false, that we need to consider here. But I will let him clarify to see
> if he has any concerns.
^ Yes exactly that. To be clear: I am happy from the s390 side with the
fix as it is proposed.
My questions were basically trying to generate the conversation that was
just had in an effort to avoid another fix later.
So, with the context provided (thanks!):
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
next prev parent reply other threads:[~2026-08-04 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 18:11 [PATCH v1] vfio/pci: Avoid mapping BARs for devices with non-mappable BARs 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
2026-07-29 21:50 ` Alex Williamson
2026-08-03 16:39 ` Farhan Ali
[not found] ` <20260803135415.2cfd37bb@shazbot.org>
2026-08-03 20:44 ` Farhan Ali
2026-08-04 13:39 ` Matthew Rosato [this message]
2026-08-04 14:09 ` Niklas Schnelle
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=e3ac5a11-b37a-48ae-b096-87f0a805cb34@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=alifm@linux.ibm.com \
--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=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