Conversation
This documents the difference between usize/u32/etc.
| - Machine-sized types (e.g., `usize`): These types should be used for a value | ||
| that should fit exactly into a register, like a abstract argument to the | ||
| `command` syscall. |
There was a problem hiding this comment.
Is this example really what we want to have? Way back when we talked about this for the 2.0 system call interface, we converged on having the current system call interface and driver traits use u32s consistently, and implement an additional, 64-bit specific trait for such platforms when we have them. I know that at least for command args, we're currently not living this reality, though we arguably ought to be.
I still think this is a good idea, because this way we don't have to reason about edge-cases on different platforms for the system call interface. Driver (interfaces) behave identically across these platforms.
I'll have to check whether the CHERI PR (tock/tock#4174) changes this.
|
@bradjc Is this just outdated / lost traction, or is there another reason why we wouldn't want to have this in the docs? |
2 participants
This documents the difference between usize/u32/etc.
No need to merge this right away until we have more of the CHERI work included.