From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=202.12.124.157 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793376067; b=M+ngRCDxngBrrYJK/eDDU9dpZssXePi4Z73Nu/Bb4u8+E5Gyqz/hfE28lytU660cJgW2 gu+VXJE89VT8nYYj5sHf9nA4l45ZHcdWVVoVLK+HgJ4Q26nrFyWmhcK6kOsCoGA2KZq4O fJiEgmWTThJJS0L7k+2HCRdy8u0YIH7Y2UyH/ODVZrvNb/B0tfPm3e7oAP12kf6UDy6I9 5u1yl//UeEt4BP5lYc71IhJU9QvbQEirhoY/gxyiKbZNuAbAnr9gu8/s+rvZ3LYxOKmdJ SEgyxSqLUTxwUcLvYWOkqYsf9hAPyz1quLCoyjEovzfbYngMqOnhhlLeLzS0rUWiGEA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793376067; h=DMARC-Filter:Received:Received:DKIM-Signature:DKIM-Signature: X-DKIM2-Info:DKIM2-Signature:X-DKIM2-Info:Message-Instance: X-ME-Sender:X-ME-Received:X-ME-Proxy-Cause:X-ME-Proxy:Feedback-ID: Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: X-Mailer:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=L89tyukt5b5c8qkH2tYN/al1Q24Aux8kILau79H19gs=; b=ZSzsadvCqxvk82SPjrgGYoaGYomvquh0H6kRSkJTnFNxbRz89WqKQJ5wu7yxF6NQJay/ VqIp2pWT40cLqom6AVX+a0VDlLx4OmGpn3NTBHgdcJI/oxFlM9NmD0Jy4RKZwmxdl9ayr MW1lEDo8NsQPIGvngl8F42teWS30aK698vnOBhuAjr2Sysnxivg0k31NKBIYDSsPAq/vH Yt1kPtHkZt45Oe2AejKwge3vIVaW90eAm3R0Y8ZvgqqoGfloVYkkSiRNEjXdgz8OK8jsq m4mFklTPzTM952QQw4kY66dXINVSkw2SoSWD8bbcvG75YOOx1zBMlodUnuioBMA/wzA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=shazbot.org; spf=pass smtp.mailfrom=shazbot.org; dkim=temperror header.d=shazbot.org header.i=@shazbot.org header.a=rsa-sha256 header.s=fm2 header.b=tieSHTdP; dkim=pass header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm2 header.b=nvCOJE9o; arc=none smtp.remote-ip=202.12.124.157 Received: from fhigh-b6-smtp.messagingengine.com (fhigh-b6-smtp.messagingengine.com [202.12.124.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CC142606A31D for ; Fri, 30 Oct 2026 16:00:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org CC142606A31D Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=shazbot.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=shazbot.org Authentication-Results: smtp.subspace.kernel.org; dkim=temperror header.d=shazbot.org header.i=@shazbot.org header.a=rsa-sha256 header.s=fm2 header.b=tieSHTdP; dkim=pass (2048-bit key, unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm2 header.b=nvCOJE9o Received: from phl-compute-08.internal (phl-compute-08.internal [10.202.2.48]) by mailfhigh.stl.internal (Postfix) with ESMTP id 3FC9C7A0130 for ; Fri, 30 Oct 2026 12:00:56 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-08.internal (MEProxy); Fri, 30 Oct 2026 12:00:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shazbot.org; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1793376054; x=1793462454; bh=L89tyukt5b5c8qkH2tYN/al1Q24Aux8kILau79H19gs=; b= tieSHTdPsW858t4IdRNruGMMvspjyjZiF94vc/xGEHiHcfWpeDldeKwA3NPeEPxc DVAeUQHx2zW7j53z0j2ztJG9dINVLq974CgIP6ueY6zIiij4OMeVN2vn3Q+eho0X 47rr+8fVr5gwLPlSdCMhrboU9w3UMgk9U7/UKJ9yHTsQBvju9Yf+t5eJggSMmG1I Auyu1Wjl+z60vuPeW8LxSOuTZNk4eHVPv3sDyx2AK53k5rE6azrIy43VIfQYdBkf HyBvn7xqjW+gJ6OYiLp22FzyJsErNElwJHCbGsqxNPjMW39N0EIvsJtYbVzaSVB/ d0cVBTHhqSdrZFEEb8fBGw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1793376054; x= 1793462454; bh=L89tyukt5b5c8qkH2tYN/al1Q24Aux8kILau79H19gs=; b=n vCOJE9opVcfH82cuieLrQLRdliOw9Fq089ErTs/2t4FftKHTJaqQtHZzYpPWRjBk F9rfX3tvwwqufQ7Ac2FT0za+ed4tjA4EBOCWFXEEmg3xoeZ3evNknENdBa9uJGH0 AyIUHsROqp9f760BrgE9TPmUAYCeuJ0rFfSrpbkZwQhZ0A1JnF9G3WnYzcH6f/N2 nn5TPg29zJq2SjwMYNwtZJoRPVwmA16/xtpM6AW6sRXff1nel1pLhZohOqmpZZYa kQ03KDvNQ81GgCWmYtPpo4kLYToQQMAnifW82OZS7rnIg/vZHLPKRATQyPzbyQxs 9uxPLrOBpIif7UcJKhnfw== X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-08; repo=github.com/dkim2wg/interop; date=2026-10-28; sw=lmtpprox; action=sign d=shazbot.org a=rsa-sha256; DKIM2-Signature: i=1; m=1; t=1793376054; d=shazbot.org; mf=PGFsZXhAc2hhemJvdC5vcmc+; rt=PGxpbnV4LXBjaUB2Z2VyLmtlcm5lbC5vcmc+; s=fm2:rsa-sha256:fz79c5KNJo1ITtWbB1n+IUfipokxhX6hiNf7XnR1cELYaZ8 4X1tKceO0cfYME76K9Z4Yu/XczVOXyj3VSnK3nam1xyrrtDWtHKI1k0MmP3HLDfI AB6Rx+ETgOtPisTJs8kWopm+tg3MPBirfcX2DIeYtkCxTlEq7+O+MjNv7aGGaeOI PcvFAMy1z+KYEdy0Q7+f2SQpRGl6MZ07I6hW7cts1v1MhGCU4Q2skHb9h6gac8aa AY+I28rwBhLJrOS/UUwjcoKHWsw3vKLaWJDa+AF9boekCuXGyJ7NIzKjgZn+COhV 8SxyVO9nSbpsn5aFVBhbpRnrNxnCyR1Fsc+NPiw==; X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-08; repo=github.com/dkim2wg/interop; date=2026-10-28; sw=lmtpprox; action=mi-m=1; hc=12; hn=cc,content-transfer-encoding,content-type,date,feedback-id, from,in-reply-to,message-id,mime-version,references,subject,to; Message-Instance: m=1; h=sha256:Dywa0nh01Y4KCxYkiW9uTIaWIurvgzJb6i3EZHfmuls=:EYti1+L3wqJp7tckEjY8frIqelFuOK5JGtGnvfzp/ag=; X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTFJuiyPAomletbDV+qdH6dBvCjjAz52xg4f2daCyYxnm8YZgRg1ZLSbQlEUf2J6lm ye3poX44/VWNiB0kcC9J1/qYYuQ2M9buv7uyYDJjj2+CIe6iQU4eT7aCWiyjzzgxexCMWq 8NKiSE292ktHs7OSAM03zbX7Vhm/uElw95rbIy1RBU+rl3y+RbGpYLbP1HsQzbWnfybCpk h5TjEaeYgL8peSmIAuQy81sXA5aCIdAbBHDSYRJbY4vdOkAj9t1VJedT7Nfuc5Gq9F5S+K QPZm0PqI1HAk/9EsPAQ/c3g/mnp/lJIjzCEGAcVTxZ4tKusllUXQwGDbUN0rGB1xSpKkcF qzJwMAUXn1HSqmTQhmy3ohqGNlzp3qjRrbCSX92d+LhCSuVsdX6BclgCZlao7qMo25+JJr 3IYil84YlCCZ3ch5oUA8/usswpis26GiagRmz6SOvgwgF5lygL76CX+TNky6fIM1HEz668 eqGtz54PFR9foDfV3/Y427dLXwoSnLn7HCYOnqLlw3IIf510Vxq/aQCpBP7hucLPEDZeSt Es/El7PPfGcjwrTn4RpBe6dluaV4mBz9sif2832STlC8dyOkgumLsp9ibbrW4wJ+sDvTGH lBsTbHJ09L1XrYWMuuMWXGNMrX2gdNwgOba5TiGN/VCh/Ce7MTj0n20B+wSw X-ME-Proxy: Feedback-ID: i03f14258:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 30 Oct 2026 12:00:51 -0400 (EDT) Date: Fri, 30 Oct 2026 10:00:50 -0600 From: Alex Williamson To: fengchengwen , Cc: , , , , , , , , , alex@shazbot.org Subject: Re: [PATCH v20 00/16] vfio/pci: Add PCIe TPH support Message-ID: <20261030100050.16df202b@shazbot.org> In-Reply-To: <6d86dd9c-83ad-4884-915e-6509995c5ba3@huawei.com> References: <20260714104325.54444-1-fengchengwen@huawei.com> <6d86dd9c-83ad-4884-915e-6509995c5ba3@huawei.com> X-Mailer: Claws Mail 4.4.0 (GTK 3.24.52; x86_64-pc-linux-gnu) X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 21 Oct 2026 09:43:05 +0800 fengchengwen wrote: > Hi Alex, > > Quick follow-up from our LPC discussion on the VFIO TPH patchset. > > The P2P TPH path carries significant verification complexity, as it builds > on the PCI P2PDMA stack which is still under active upstream revision. > > Meanwhile there is clear real-world demand for the device-to-host scenario. > AMD recently posted their debugfs series exposing CPU-to-ST mappings [1], > and we also have strong use cases for D2H TPH enablement. You might be working ahead of the industry. The debugfs interface provides evidence that the feature is coming, but is perhaps still working through implementation pains. The lack of community participation in the vfio interface actually suggests to me that there isn't a great real-world demand for this feature, yet. > I'd like to propose a phased upstream approach: > land device-to-host support first, and defer P2P TPH to a follow-up series. > > We can add P2P support cleanly on top once the interface and verification > are solid. This way we can deliver usable TPH functionality sooner, while > keeping the path open for full P2P support later. > > Let me know your thoughts on going ahead with device-to-host support first. > If you're okay with this, I'll post v21 accordingly. As above, the demand is not apparent based on the lack of community participation in these threads. I'm reluctant to commit to a uAPI that's largely been proposed by me, as the maintainer, trying to fill gaps in the narrow scope of the original proposal. This needs support from the community and validation across broader use cases. I think that's the actual barrier, rather than ordering versus Zhiping's series. Despite the LPC talk, there still hasn't been much engagement on the question of whether device ownership grants the user the ability to target specific cache levels and how we handle cases where the driver:cpu association isn't static. Thanks, Alex