[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aOR5juzHnsK2E40z@archie.me>
Date: Tue, 7 Oct 2025 09:23:10 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Roman Kisel <romank@...ux.microsoft.com>, arnd@...db.de, bp@...en8.de,
corbet@....net, dave.hansen@...ux.intel.com, decui@...rosoft.com,
haiyangz@...rosoft.com, hpa@...or.com, kys@...rosoft.com,
mikelley@...rosoft.com, mingo@...hat.com, tglx@...utronix.de,
Tianyu.Lan@...rosoft.com, wei.liu@...nel.org, x86@...nel.org,
linux-hyperv@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Cc: benhill@...rosoft.com, bperkins@...rosoft.com, sunilmut@...rosoft.com
Subject: Re: [PATCH hyperv-next v6 01/17] Documentation: hyperv: Confidential
VMBus
On Fri, Oct 03, 2025 at 03:26:54PM -0700, Roman Kisel wrote:
> +The data is transferred directly between the VM and a vPCI device (a.k.a.
> +a PCI pass-thru device, see :doc:`vpci`) that is directly assigned to VTL2
> +and that supports encrypted memory. In such a case, neither the host partition
Nit: You can also write the cross-reference simply as vpci.rst.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists