[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z9B_yS_d8ny9hYUX@example.org>
Date: Tue, 11 Mar 2025 19:24:09 +0100
From: Alexey Gladkov <legion@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Jürgen Groß <jgross@...e.com>,
Joerg Roedel <jroedel@...e.de>, Joerg Roedel <joro@...tes.org>,
"Alexey Gladkov (Intel)" <alexey.gladkov@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>, 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 Tue, Mar 11, 2025 at 12:07:48PM +0100, Borislav Petkov wrote:
> On Tue, Mar 11, 2025 at 11:22:23AM +0100, Jürgen Groß wrote:
> > I can live with that, as long as we make it possible to make e.g.
> > /sys/guest/xen a link to /sys/hypervisor (if xen is the hypervisor
> > the guest is directly running on). This means that /sys/guest/*/type
> > should not conflict with /sys/hypervisor/type.
>
> Yeah, so Joerg and I came up with this on IRC:
>
> /sys/hypervisor/{sev,tdx}
This directory is for guest-side information, right ?
>
> * It should not disturb the current hierarchy there
>
> * No need for a new hierarchy like /sys/guest - we haz enough and besides,
> /sys/hypervisor sounds like the right place already
The /sys/hypervisor is for host-side information ?
>
> * ...
>
> So yeah, I guess we can try this.
If the answers to both questions are yes. Then I have understood
everything correctly and I agree with it.
--
Rgrds, legion
Powered by blists - more mailing lists