diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-09-21 17:17:24 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-09-21 17:17:24 +0200 |
| commit | 67c3ee6db50e51738c01b0b88b40288fdf08ead3 (patch) | |
| tree | 198c323c3166e83f97378a3b2b77668f92f40dd1 | |
| parent | a5adeb318c621f354cd0fd46e466d15a1514e133 (diff) | |
document a bit about virtio drivers
| -rw-r--r-- | contributing.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index 47da1d40..641de8b5 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -101,7 +101,7 @@ access to it from userland. exec would probably call it from `hurd/exec/exec.c`, which exposes the partitions of the disk image, using parted, and the parted-based storeio (`settrans -c foos1 /hurd/storeio -T typed part:1:file:/home/samy/tmp/foo`). This would be libnetfs-based. -* Write virtio drivers for KVM. Ideally they would be userland. +* Write virtio drivers for KVM. Ideally they would be userland. That means getting documented about how virtio works, and implement it. The hurdish part is mostly about exposing the driver interface. The devnode translator can be used as a skeleton. * Port valgrind. There is a whole [[GSoC proposal|community/gsoc/project_ideas/valgrind ]] about this, but the basic port could be small. |