Philipp Oppermann

Thanks a lot! I'm glad that you like it. Yes, my current plan is heap allocation, then multitasking (async/await, threads, kernel processes), and after that userspace processes (ring 3, syscalls)....

@Darksecond I think a higher-half kernel is probably the easiest approach as it only needs a minimum of context switches. I'm still debating whether we should add something like [kernel...

> I'm not totally sure yet. Currently I'm leaning towards a normal higher-half approach. Ok, seems like we're on the same page then. Let me know if you find another...

It's on my list, yes. There's just so much else to do that I don't know when I'll get to it.

Cool, didn't know about this reconnect trick, thanks! I think we should mention it in the “Set Up Gdb” post. Regarding `rust-gdb`: Yeah, it is included for a long time....

> I'm not familiar with this calling convention, but would suspect that having an i128 argument just doesn't make sense for it and rustc may be the party responsible for...

> I don't think FnOnce works in this signature. Why not? The function would only handle a single packet per call (like it does today), so it would only invoke...

Ok, then I misunderstood the interface and we need `FnMut`.

It's worth noting that running binaries of arbitrary dependencies is already possible, using a small hack: 1. Use `cargo metadata` or the [`cargo_metadata`](https://docs.rs/cargo_metadata/0.14.0/cargo_metadata/) crate to find the folder where `cargo`...

> To be sure I understand, this RFC is not proposing any specific interrupt ABI, but simply talking about the _idea_ of interrupt handler ABIs and what their requirements would...