Gerwin Klein

Still on my todo list, but not very high up in priority.

> Is still relevant? It's relevant in the sense that this will fail for python 3.6 and earlier. We should check what the default versions are for the current Debian...

@axel-h this is still on draft, but seems otherwise ready to merge. Are we good to go ahead on this one? If yes, can you please switch off draft mode?

> The open point here is running this though a checker regularly. Currently, as @Indanz remarked, it is more or less an informative comment only and Python lacks a nice...

Thanks for testing it, but I don't want to mix in a checker into this PR. Adding a checker would be a TSC decision (which checker(s), what rules, which repos,...

I think we should close this PR, it refactors too much code without clear need for kernel-level changes. There are some parts that would be valuable to include without the...

@alwin-joshy can you please rebase and resolve conflicts first before we look into it more closely? Just want to make sure the test are running on the latest version.

I agree, the current policy is that init task is fully trusted and must be high assurance or a high assurance system. Making the kernel code more complex to guard...

The ultimate right (including masks etc) is only in the page table entries, so I guess we do have to walk the table, yes. Is the plan to put the...

Ah, for flushing we're setting the address space to be flushed to be current for the flush anyway, so that part is all good.