[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20d483b6-da24-4ddc-b6d4-c0c23b8e5ea2@app.fastmail.com>
Date: Tue, 04 Oct 2022 10:35:38 -0700
From: "Andy Lutomirski" <luto@...nel.org>
To: "Ali Raza" <aliraza@...edu>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Cc: "Jonathan Corbet" <corbet@....net>, masahiroy@...nel.org,
michal.lkml@...kovi.net,
"Nick Desaulniers" <ndesaulniers@...gle.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Ingo Molnar" <mingo@...hat.com>, "Borislav Petkov" <bp@...en8.de>,
"Dave Hansen" <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Kees Cook" <keescook@...omium.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
"Al Viro" <viro@...iv.linux.org.uk>,
"Arnd Bergmann" <arnd@...db.de>, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
"Steven Rostedt" <rostedt@...dmis.org>,
"Ben Segall" <bsegall@...gle.com>, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com,
"Paolo Bonzini" <pbonzini@...hat.com>, jpoimboe@...nel.org,
linux-doc@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-arch@...r.kernel.org,
"the arch/x86 maintainers" <x86@...nel.org>, rjones@...hat.com,
munsoner@...edu, tommyu@...edu, drepper@...hat.com,
lwoodman@...hat.com, mboydmcse@...il.com, okrieg@...edu,
rmancuso@...edu
Subject: Re: [RFC UKL 09/10] exec: Give userspace a method for starting UKL process
On Mon, Oct 3, 2022, at 3:21 PM, Ali Raza wrote:
> From: Eric B Munson <munsoner@...edu>
>
> From: Eric B Munson <munsoner@...edu>
>
> The UKL process might depend on setup that is to be done by user space
> prior to its initialization. We need a way to let userspace signal that it
> is ready for the UKL process to run. We will have setup a special name for
> this process in the kernel config and if this name is passed to exec that
> will start the UKL process. This way, if user space setup is required we
> can be sure that the process doesn't run until explicitly started.
This is just bizarre IMO. Why is there one single UKL process?
How about having a way to start a UKL process and then, if desired, start *another* UKL process? (And obviously there would be a security mode in which only a UKL process that is actually part of the kernel image can run or that only a UKL process with a hash that's part of the kernel image can run.)
--Andy
Powered by blists - more mailing lists