[Feature]: ioctl for small reset-safe transfers #171
Description
Is your feature request related to a problem? Please describe.
Non-ML device management tools want IO that is safe in the face of device reset and are willing to give up throughput and latency to get it.
Describe the Solution You'd Like
ioctls for 1/2/4/8 byte NOC read & write.
Describe Alternatives You've Considered
Requiring the app to handle SIGBUS when it accesses the zapped MMIO mapping.
Why is this Feature Important?
Long-running telemetry apps should be robust. Robustness requires simplicity.
Proposed Design/Technical Details (Optional)
Target address is X+Y+local address. Consider also future hardware without X & Y coordinates.
Address must be size-aligned.
KMD isn't able to check the validity of the address.
Use Cases
UMD is the direct user. It would use this to provide simple reset-safe operations.
Additional Context
Pavle earlier proposed NOC read/write32 ioctls.