[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D5A4D31B-4A37-48B7-8EBC-C8A4062B4813@alien8.de>
Date: Thu, 30 May 2024 19:06:12 +0200
From: Borislav Petkov <bp@...en8.de>
To: Tom Lendacky <thomas.lendacky@....com>
CC: linux-kernel@...r.kernel.org, x86@...nel.org, linux-coco@...ts.linux.dev,
svsm-devel@...onut-svsm.dev, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Dan Williams <dan.j.williams@...el.com>, Michael Roth <michael.roth@....com>,
Ashish Kalra <ashish.kalra@....com>
Subject: Re: [PATCH v4 09/15] x86/sev: Provide guest VMPL level to userspace
On May 28, 2024 11:08:35 PM GMT+02:00, Tom Lendacky <thomas.lendacky@....com> wrote:
>I can move it there. Or what about creating a coco folder under /sys/kernel/? This would then create /sys/kernel/coco/sev/?
>
Sysfs hierarchy is special - can't just add stuff willy nilly. This doc hints at that:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/sysfs.rst
And then those things get documented here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI
and supported forever and ever until the end of time.
So the usage needs to be precisely documented and weighed whether we really need it...
Thx.
--
Sent from a small device: formatting sucks and brevity is inevitable.
Powered by blists - more mailing lists