On Wed, Feb 14, 2024 at 05:31:12PM +0100, Petr Tesařík wrote: > On Wed, 14 Feb 2024 16:11:05 +0100 > Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > On Wed, Feb 14, 2024 at 03:55:24PM +0100, Petr Tesařík wrote: > > > OK, so why didn't I send the whole thing? > > > > > > Decomposition of the kernel requires many more changes, e.g. in linker > > > scripts. Some of them depend on this patch series. Before I go and > > > clean up my code into something that can be submitted, I want to get > > > feedback from guys like you, to know if the whole idea would be even > > > considered, aka "Fail Fast". > > > > We can't honestly consider this portion without seeing how it would > > work, as we don't even see a working implementation that uses it to > > verify it at all. > > > > The joy of adding new frameworks is that you need a user before anyone > > can spend the time to review it, sorry. > > Thank your for a quick assessment. Will it be sufficient if I send some > code for illustration (with some quick&dirty hacks to bridge the gaps), > or do you need clean and nice kernel code? Given that code is going to need a rewrite to make use of this anyways - why not just do the rewrite in Rust? Then you get memory safety, which seems to be what you're trying to achieve here. Or, you say this is for when performance isn't critical - why not a user mode helper?
