Guiding plan:

Prioritize core code, such as epoll and posix file objects. We may end up having to migrate surrounding code during the process anyway.

Remaining descriptors and related status listeners and syscall condition are core bits used by many syscalls, so this is medium/high priority. But there are some dependencies so we'd want a specific order.
Dependency order for migrating remaining descriptors:

1. remaining descriptors (excluding epoll)
   a. regular file (close to direct translation, with some improvements - see below)
   b. timerfd
   c. udp - step 6 on Steve's networking list
   d. tcp (wrapped version) - requires steps 1-5 in Steve's networking list.
2. epoll/poll/select (edit: no longer depends on 1. as of 2023-02-14)
3. remove CompatFile
4. futex / futex table
5. syscall condition (edit: depends on 4, but no longer depends on 1. as of 2023-02-14)
6. remove unused status listener

Modules

shim

• not blocking new code from being in Rust, but would be nice to make more maintainable and understandable

shmem

• pretty well modularized and has a rust API. low priority.

cpu affinity

• pretty modularized
• probably want at least a rust wrapper API
• rewriting internal C code is lower priority.

futex and futextable

• futex has a list of c status listeners syscall condition; need to add support for rust listeners
• futextable is mostly a wrapper around glib hash table
• will want to support both rust and c status listeners first, until no one needs the c listener path anymore

netif and qdisc

• see "steven's plan for migrating network code"
• need to enable support for rust descriptors first
• full rewrite happens later
• netif design change:
  • associate should return a handle, which will disassociate when dropped
  • sockets that bind on both default and localhost will need to store both handles

syscall handler framework, and specific handlers

• remove the syscallhandler_execve?
• syscall_handler.c should be able to be converted to syscall/handler/mod.rs, from there the match statement can call syscall functions implemented in C or Rust.
• converting non-core syscalls (e.g. time related calls) are lower priority since those are easier to convert later
• should shadow syscalls that take fds specify them as int or uint?
  • strace macro will still print signed
  • try to get try_into() working so we don't have to specify int or uint