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 BBA843B388E; Tue, 31 Mar 2026 14:14:00 +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=1774966440; cv=none; b=uj+KkhSBlw9Hik++lU1lMJnTecqnhshYd1/bkg4iaoHVT5Pi1yINuf0iBvLeHj1QW91EOBW6RFYUCQROmIU8mB/3L/vYdikrVLnai9Kqj2UJonQ9XeNa0GY4GVl01xehfB8WRr4UffDLbu0ckLL7ShLiZZaDl6yFibIQfA9nb7Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774966440; c=relaxed/simple; bh=WuDTh1qvVfpreyA+FwkOQW5WOW/1M6AkJSQhmwhXYQk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=PIti58WNiX734+ivxl0mt6ZsCsDj3OLcSnuKdWbt9Z+MFfUJBm5CGQk+m9vcCnOIJ+maW4UwrCyM8mQh/wTuzbYjJCBmn3gK+BmclrqT1TNiy454F1WuecIZML+rjSzDElibK9ZZLFVIFj/+KB1jwj2xfqq5PN/ecYrNnbXAQLU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LzRtQzHM; 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="LzRtQzHM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E590CC19423; Tue, 31 Mar 2026 14:13:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774966440; bh=WuDTh1qvVfpreyA+FwkOQW5WOW/1M6AkJSQhmwhXYQk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LzRtQzHM+7ul0hm/xfo7NgRoHCrt2OsiKzgRPhjDXdWwcxZjjMA1P5HJP8+thKeSW dCZGnt2cfmJYCJbx98mUnoWzGgRzMfMJF2stE704IIgW7Tbjgn72daUYEYUry8Gmdy R8tCM+cdqhYylcd1eMFh+0+fIMAuEvhIYQC/4ADz7OL7uwS0JgIFfh9OJzC+/6zn/W VLoTaYI7N0MTfj5Gy52dDY/TJpv4+V4DS/SkF8E1cEIMSB4RKLDsZKgG39HAc4uk5P 9MD72pRxxmuRylRmH+eDnH0Dyh7f1qRJkvRsUmOIpXJo9oT68WCv6AHCtRXSjeOilT nobVfwLzY6fow== Date: Tue, 31 Mar 2026 08:13:58 -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-1-zhipingz@meta.com> <20260324234615.3731237-2-zhipingz@meta.com> <20260325082534.GN814676@unreal> <20260331083758.GA814676@unreal> <20260331132942.GC814676@unreal> <20260331140309.GH814676@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: <20260331140309.GH814676@unreal> On Tue, Mar 31, 2026 at 05:03:09PM +0300, Leon Romanovsky wrote: > I understand, my proposal is always set TPH flag when new struct is > used. An existing application recompiled against the new kernel api implicitly uses the new struct layout without setting the TPH flag, so kernel and application are out of sync on where dma_ranges exists with your proposal.