From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5080D3A75A8; Tue, 31 Mar 2026 19:44:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774986245; cv=none; b=VOxIcjkU0eba2qskcSrnNd4D1UBrPA6rjfU4h76bZRMxKM2dKPAzFkwP9w+OPAzJeRxGUfQacNRbw5MTVoF9GJ44SR7yVxPjj+jW4CYNgR9sNHr49kM6MH0ZSkhNgJCYK1WeOfKZcHgq2iy8AkBfNY9IzH6tZyDnh85+nPaAGlA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774986245; c=relaxed/simple; bh=jGGUJKYrNdV8MrZToA2w5hj3QV82YHccM4CmlfqrLZI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=hjodHXR8mOEzrzyR8QXkdBauEsq1LG3GOZdeFkQKcRb3eG+WiMOAof10RhEplvGOA0RTHZf0E7olkmdQ155jSoAHEg9IZHmsoLn7ycJCAfu2HyalSRglSO2nqZ6O5qlSYJQpgHfEsr/x3cOrC2cDFk75HHqjy+sco5q9EZd5bOk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Q3/LFlfZ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Q3/LFlfZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B3F5EC2BCB2; Tue, 31 Mar 2026 19:44:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774986245; bh=jGGUJKYrNdV8MrZToA2w5hj3QV82YHccM4CmlfqrLZI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Q3/LFlfZuSyNzsTx+6YfPrMA8hjusRnQdSbDNm1uLtyw2tdOl0S/wuHE+sPFUrKHx vBNdpyBqm5EjQXRbJgCLoKwCwUAA15df0M2MJ4HLq0fsV83v8LW5RC2oDT7aAA8UJX 8bwdTpDVolQoPS0sF48lnz0DXH2mUiVAMxuLpmkeg+L/uviUi4p2NGmHjqjTk1cKzT bHeWYYJNPnXHa7hhXi9pjF0M2I52ntniXF0Q2sYFxQHqZxfNtd+0ftCaxZ222xj++W XZDKarZ7rwu30MFv95BHt8xBnzedg3sCeHRf8SxbEAoBXu9PHr+rCW/ubZAfxD4z+g 4RbgcSXcTlBRA== Date: Tue, 31 Mar 2026 13:44:02 -0600 From: Keith Busch To: Leon Romanovsky Cc: Zhiping Zhang , Jason Gunthorpe , Bjorn Helgaas , linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org, netdev@vger.kernel.org, dri-devel@lists.freedesktop.org, Yochai Cohen , Yishai Hadas , Bjorn Helgaas Subject: Re: [RFC v2 1/2] vfio: add callback to get tph info for dmabuf Message-ID: References: <20260324234615.3731237-2-zhipingz@meta.com> <20260325082534.GN814676@unreal> <20260331083758.GA814676@unreal> <20260331132942.GC814676@unreal> <20260331140309.GH814676@unreal> <20260331190220.GI814676@unreal> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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.