From: Matt Evans <mattev@meta.com>
To: Alex Williamson <alex@shazbot.org>
Cc: Leon Romanovsky <leon@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Kevin Tian <kevin.tian@intel.com>,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
Ankit Agrawal <ankita@nvidia.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
schnelle@linux.ibm.com
Subject: Re: [PATCH] vfio/pci: Don't export DMABUFs for unmappable BARs
Date: Tue, 21 Apr 2026 18:50:49 +0100 [thread overview]
Message-ID: <2487afab-779a-46fe-9f85-4e36748cd9b5@meta.com> (raw)
In-Reply-To: <789793ec-8ee7-4cba-b20e-15f8bb6f494d@meta.com>
Hi,
On 20/04/2026 15:24, Matt Evans wrote:
> Hi Alex,
>
> On 17/04/2026 23:31, Alex Williamson wrote:
>> [snip]
>>
>> That's fixing the leaf driver rather than the subsystem, where
>> pci/p2pdma really ought to honor its own flag indicating the BAR is not
>> mappable. The precedent is already there in rejecting IO BARs. Thanks,
>
> All good; I appreciate the discussion, thanks, and will redo with
> checking non_mappable_bars in p2pdma.
Since the patch has a radically different subject/lists, here's a courtesy link:
https://lore.kernel.org/linux-pci/20260421174351.3897842-1-mattev@meta.com/
(Obviously we can drop this thread now.)
Matt
prev parent reply other threads:[~2026-04-21 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 18:16 [PATCH] vfio/pci: Don't export DMABUFs for unmappable BARs Matt Evans
2026-04-15 18:23 ` Leon Romanovsky
2026-04-16 8:11 ` Leon Romanovsky
2026-04-16 13:05 ` Matt Evans
2026-04-16 13:14 ` Leon Romanovsky
2026-04-16 18:03 ` Matt Evans
2026-04-16 21:48 ` Alex Williamson
2026-04-17 14:25 ` Matt Evans
2026-04-17 22:31 ` Alex Williamson
2026-04-20 14:24 ` Matt Evans
2026-04-21 17:50 ` Matt Evans [this message]
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=2487afab-779a-46fe-9f85-4e36748cd9b5@meta.com \
--to=mattev@meta.com \
--cc=alex@shazbot.org \
--cc=ankita@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=vivek.kasireddy@intel.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