Re: [PATCH v1 01/40] *** HACK *** linux-headers: Update headers to pull in TDX API changes

Xiaoyao Li
2022-08-02T10:38:46Z

On 8/2/2022 5:47 PM, Daniel P. Berrangé wrote:
> On Tue, Aug 02, 2022 at 03:47:11PM +0800, Xiaoyao Li wrote:
>> Pull in recent TDX updates, which are not backwards compatible.
>>
>> It's just to make this series runnable. It will be updated by script
>>
>> scripts/update-linux-headers.sh
>>
>> once TDX support is upstreamed in linux kernel.
>
> I saw a bunch of TDX support merged in 5.19:
>
> commit 3a755ebcc2557e22b895b8976257f682c653db1d
> Merge: 5b828263b180 c796f02162e4
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Mon May 23 17:51:12 2022 -0700
>
> Merge tag 'x86_tdx_for_v5.19_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
>
> Pull Intel TDX support from Borislav Petkov:
> "Intel Trust Domain Extensions (TDX) support.
>
> This is the Intel version of a confidential computing solution called
> Trust Domain Extensions (TDX). This series adds support to run the
> kernel as part of a TDX guest. It provides similar guest protections
> to AMD's SEV-SNP like guest memory and register state encryption,
> memory integrity protection and a lot more.
>
> Design-wise, it differs from AMD's solution considerably: it uses a
> software module which runs in a special CPU mode called (Secure
> Arbitration Mode) SEAM. As the name suggests, this module serves as
> sort of an arbiter which the confidential guest calls for services it
> needs during its lifetime.
>
> Just like AMD's SNP set, this series reworks and streamlines certain
> parts of x86 arch code so that this feature can be properly
> accomodated"
>
>
> Is that sufficient for this patch, or is there more pending out of
> tree that QEMU still depends on ?

That's TDX guest support, i.e., running Liunx as TDX guest OS.

What QEMU needs is TDX KVM support and that hasn't been merged yet.

> With regards,
> Daniel