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] [thread-next>] [day] [month] [year] [list]

Message-ID: <724f9f7d-137b-4cf5-aff5-bbb9727c23c1@oracle.com>
Date: Thu, 10 Apr 2025 22:24:56 +0530
From: ALOK TIWARI <alok.a.tiwari@...cle.com>
To: Roman Kisel <romank@...ux.microsoft.com>, 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
Cc: apais@...rosoft.com, benhill@...rosoft.com, bperkins@...rosoft.com,
        sunilmut@...rosoft.com
Subject: Re: [PATCH hyperv-next 1/6] Documentation: hyperv: Confidential VMBus



On 09-04-2025 05:38, Roman Kisel wrote:
>   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.
> +

typo trsuted  -> trusted

> +To support confidential communication with the paravisor, a VmBus client
> +will first attempt to use regular, non-isolated mechanisms for communication.
> +To do this, it must:


Thanks,
Alok