[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z87ce37GjCqpOLCW@8bytes.org>
Date: Mon, 10 Mar 2025 13:35:07 +0100
From: Joerg Roedel <joro@...tes.org>
To: Juergen Gross <jgross@...e.com>
Cc: Alexey Gladkov <legion@...nel.org>,
"Alexey Gladkov (Intel)" <alexey.gladkov@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>, Borislav Petkov <bp@...en8.de>,
Joerg Roedel <jroedel@...e.de>, Ingo Molnar <mingo@...nel.org>,
x86@...nel.org, hpa@...or.com,
Tom Lendacky <thomas.lendacky@....com>,
Nikunj A Dadhania <nikunj@....com>, linux-kernel@...r.kernel.org,
Larry.Dewey@....com
Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS
On Mon, Mar 10, 2025 at 01:28:38PM +0100, Juergen Gross wrote:
> We can (saying that with my Xen maintainer hat on).
>
> There is /sys/hypervisor/type which should return the used virtualization
> environment ("xen" when running as a Xen guest).
In CoCo environments there can be more than one hypervisor beneath the
guest. For example KVM as the untrusted host, SVSM or another para-visor
as the trusted in-guest hypervisor. On TDX there is also the TDX module
in-between, which is another level of hypervisors. ARM and Risc-V will
have similar architectures.
Regards,
Joerg
Powered by blists - more mailing lists