Nick Spinale

> I noticed that ./crates/sel4-platform-info/Cargo.toml depends on serde and serde_yaml which in turn depends on [unsafe_libyaml](https://crates.io/crates/unsafe-libyaml) which is a [c2rust](https://github.com/immunant/c2rust) transpiled unsafe Rust code (which is kind of cool) Interesting....

> Something that may be worth considering is supporting configurations that use pre-built code-gen outputs that can be checked into a VCS system and manually inspected. @kent-mcleod can you elaborate...

I don't think so. For reference, here are the sizes of each target's stdlib on my machine: ``` du -sh ~/.rustup/toolchains/1.79.0-x86_64-unknown-linux-gnu/lib/rustlib/{x8 6_64-unknown-linux-musl,x86_64-apple-darwin,aarch64-apple-darwin} 196M x86_64-unknown-linux-musl 115M x86_64-apple-darwin 110M aarch64-apple-darwin ```

That would work. Another option would be to have a toolchain file with no targets and use -Zbuild-std. But I think the env var idea is better.

I agree. I think that specifying a MSRV basically solves the problem this issue is actually about without introducing any new problems like those related to the toolchain file that...

I've updated the PR. I've also moved code around to minimize the diff to make it easier to review. If it is going to be accepted, I'll reorganize the code...

I've updated this PR on top of https://github.com/seL4/microkit/pull/337

> If you copied the data section to a read-only area of the same size after linking, and have the program use that to init its data section at startup,...

This change would not break nor otherwise affect the Rust kernel loader.

Good catch, thanks! Indeed pointers to the initial `SchedControl` caps (one per node) are provided via the bootinfo struct instead: https://github.com/seL4/seL4/blob/019e4b608f02320f567e32fe09b48423aaeff92f/libsel4/include/sel4/bootinfo_types.h#L72