linux-kernel - Re: [PATCH hyperv-next 1/6] Documentation: hyperv: Confidential VMBus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aAssMxyM-TBnyARj@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
Date: Fri, 25 Apr 2025 06:31:15 +0000
From: Wei Liu <wei.liu@...nel.org>
To: Roman Kisel <romank@...ux.microsoft.com>
Cc: aleksander.lobakin@...el.com, andriy.shevchenko@...ux.intel.com,
	arnd@...db.de, bp@...en8.de, catalin.marinas@....com,
	corbet@....net, dakr@...nel.org, dan.j.williams@...el.com,
	dave.hansen@...ux.intel.com, decui@...rosoft.com,
	gregkh@...uxfoundation.org, haiyangz@...rosoft.com, hch@....de,
	hpa@...or.com, James.Bottomley@...senpartnership.com,
	Jonathan.Cameron@...wei.com, kys@...rosoft.com, leon@...nel.org,
	lukas@...ner.de, luto@...nel.org, m.szyprowski@...sung.com,
	martin.petersen@...cle.com, mingo@...hat.com, peterz@...radead.org,
	quic_zijuhu@...cinc.com, robin.murphy@....com, tglx@...utronix.de,
	wei.liu@...nel.org, will@...nel.org, iommu@...ts.linux.dev,
	linux-arch@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-doc@...r.kernel.org, linux-hyperv@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	x86@...nel.org, apais@...rosoft.com, benhill@...rosoft.com,
	bperkins@...rosoft.com, sunilmut@...rosoft.com
Subject: Re: [PATCH hyperv-next 1/6] Documentation: hyperv: Confidential VMBus

On Tue, Apr 08, 2025 at 05:08:30PM -0700, Roman Kisel wrote:
> Define what the confidential VMBus is and describe what advantages
> it offers on the capable hardware.
> 
> Signed-off-by: Roman Kisel <romank@...ux.microsoft.com>
> ---
>  Documentation/virt/hyperv/vmbus.rst | 41 +++++++++++++++++++++++++++++
>  1 file changed, 41 insertions(+)
> 
> diff --git a/Documentation/virt/hyperv/vmbus.rst b/Documentation/virt/hyperv/vmbus.rst
> index 1dcef6a7fda3..f600e3d09800 100644
> --- a/Documentation/virt/hyperv/vmbus.rst
> +++ b/Documentation/virt/hyperv/vmbus.rst
> @@ -324,3 +324,44 @@ rescinded, neither Hyper-V nor Linux retains any state about
>  its previous existence. Such a device might be re-added later,
>  in which case it is treated as an entirely new device. See
>  vmbus_onoffer_rescind().
> +
> +Confidential VMBus
> +------------------
> +
> +The confidential VMBus provides the control and data planes where
> +the guest doesn't talk to either the hypervisor or the host. Instead,
> +it relies on the trusted paravisor. The hardware (SNP or TDX) encrypts
> +the guest memory and the register state also measuring the paravisor
> +image via using the platform security processor to ensure trsuted and
> +confidential computing.
> +
> +To support confidential communication with the paravisor, a VmBus client

Please be consistent. In this document I see VMBus and VmBus. We should
stick with only one form.

Wei.