Tracking issue for low level device model - Githubissues

twizzler-operating-system / twizzler

The Twizzler Operating System

BSD 3-Clause "New" or "Revised" License

66 stars 14 forks source link

Tracking issue for low level device model #82

Open dbittman opened 2 years ago

dbittman commented 2 years ago

Tracking issue for RFC 0004 -- low level device model. Links: PR, Rendered

Steps

[ ] Implement RFC
- [ ] Kernel-side device tree management
- [ ] Kernel-side device tree access
- [ ] Userspace data structures and device abstraction
[ ] Complete documentation
- [ ] API docs
- [ ] Twizzler developer guide

Unresolved Questions

[ ] 1. Is the interrupt mechanism sufficient (for now) to allow effective programming of devices?
[ ] 2. What is the correct security model to apply here? Probably a set a approved programs can access the device tree and that's it.
[ ] 3. Some PCIe devices should have their memory mapped as write-combining (framebuffers, for example), but PCIe doesn't encode this information in the BARs. We need a way for userspace to perhaps remap a BAR as WC.

Implementation History

https://github.com/twizzler-operating-system/twizzler/pull/81