From: Keith Busch <kbusch@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Zhiping Zhang <zhipingz@meta.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Yochai Cohen <yochai@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [RFC v2 1/2] vfio: add callback to get tph info for dmabuf
Date: Tue, 31 Mar 2026 13:44:02 -0600 [thread overview]
Message-ID: <acwkAo2k41xaxdTS@kbusch-mbp> (raw)
In-Reply-To: <20260331190220.GI814676@unreal>
On Tue, Mar 31, 2026 at 10:02:20PM +0300, Leon Romanovsky wrote:
>
> Right, what about adding TPH fields to struct vfio_region_dma_range
> instead of struct vfio_device_feature_dma_buf?
You might have to show me with code what you're talking about because I
can't see any way we can add fields to any struct here without breaking
backward compatibility.
If we can't claim bits out of the unused "flags" field for this feature,
then my initial reply is the only sane approach: we can introduce a new
feature and struct for it that closely mirrors the existing one, but
with the extra hint fields.
next prev parent reply other threads:[~2026-03-31 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260324234615.3731237-1-zhipingz@meta.com>
[not found] ` <20260324234615.3731237-2-zhipingz@meta.com>
2026-03-25 8:25 ` [RFC v2 1/2] vfio: add callback to get tph info for dmabuf Leon Romanovsky
2026-03-26 22:41 ` Keith Busch
2026-03-26 22:55 ` Zhiping Zhang
2026-03-31 8:39 ` Leon Romanovsky
2026-03-31 8:37 ` Leon Romanovsky
2026-03-31 13:00 ` Keith Busch
2026-03-31 13:29 ` Leon Romanovsky
2026-03-31 13:35 ` Keith Busch
2026-03-31 14:03 ` Leon Romanovsky
2026-03-31 14:13 ` Keith Busch
2026-03-31 19:02 ` Leon Romanovsky
2026-03-31 19:44 ` Keith Busch [this message]
2026-03-28 2:21 ` fengchengwen
2026-03-31 0:49 ` Zhiping Zhang
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=acwkAo2k41xaxdTS@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yishaih@nvidia.com \
--cc=yochai@nvidia.com \
--cc=zhipingz@meta.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