[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DA9AU3OBT29Z.3CX827C91I3IH@nvidia.com>
Date: Fri, 30 May 2025 15:59:03 +0900
From: "Alexandre Courbot" <acourbot@...dia.com>
To: "Greg KH" <gregkh@...uxfoundation.org>
Cc: "Danilo Krummrich" <dakr@...nel.org>, "Timur Tabi" <timur@...nel.org>,
"John Hubbard" <jhubbard@...dia.com>, "Miguel Ojeda" <ojeda@...nel.org>,
"Alex Gaynor" <alex.gaynor@...il.com>, "Boqun Feng" <boqun.feng@...il.com>,
"Gary Guo" <gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, "Benno Lossin" <benno.lossin@...ton.me>,
"Andreas Hindborg" <a.hindborg@...nel.org>, "Alice Ryhl"
<aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
<linux-kernel@...r.kernel.org>, <rust-for-linux@...r.kernel.org>
Subject: Re: [PATCH] rust: add basic ELF sections parser
On Fri May 30, 2025 at 3:22 PM JST, Greg KH wrote:
> On Fri, May 30, 2025 at 09:58:02AM +0900, Alexandre Courbot wrote:
>> However, Nova also supports a couple of older chip generations that use
>> the same GSP firmware - it is for these that the ELF unpacking must
>> occur in the kernel. IIUC this has to do with the capabilities of the
>> microcontroller that ultimately does the loading (more capable RISC-V on
>> Hopper+ vs. older and more limited Falcon).
>
> Why specifically does the kernel have to get involved here? What
> requires it to do it that userspace can not?
I don't know of a user-space tool that is readily available and could
perform such extraction of the ELF content upon kernel request. Is there
anything like this?
Powered by blists - more mailing lists