Re: [RFC PATCH] docs/devel: start documenting writing VirtIO devices

2022-04-05 Thread Alex Bennée
Cornelia Huck writes: > On Wed, Mar 16 2022, Alex Bennée wrote: > >> Cornelia Huck writes: >> >>> On Wed, Mar 09 2022, Alex Bennée wrote: > +Writing VirtIO backends for QEMU + + +This document attempts to outline the information a developer

Re: [RFC PATCH] docs/devel: start documenting writing VirtIO devices

2022-04-05 Thread Cornelia Huck
On Wed, Mar 16 2022, Alex Bennée wrote: > Cornelia Huck writes: > >> On Wed, Mar 09 2022, Alex Bennée wrote: >>> +Writing VirtIO backends for QEMU >>> + >>> + >>> +This document attempts to outline the information a developer needs to >>> +know to write backends

Re: [RFC PATCH] docs/devel: start documenting writing VirtIO devices

2022-03-16 Thread Alex Bennée
Cornelia Huck writes: > On Wed, Mar 09 2022, Alex Bennée wrote: > >> While writing my own VirtIO devices I've gotten confused with how >> things are structured and what sort of shared infrastructure there is. >> If we can document how everything is supposed to work we can then >> maybe start c

Re: [RFC PATCH] docs/devel: start documenting writing VirtIO devices

2022-03-09 Thread Cornelia Huck
On Wed, Mar 09 2022, Alex Bennée wrote: > While writing my own VirtIO devices I've gotten confused with how > things are structured and what sort of shared infrastructure there is. > If we can document how everything is supposed to work we can then > maybe start cleaning up inconsistencies in the

[RFC PATCH] docs/devel: start documenting writing VirtIO devices

2022-03-09 Thread Alex Bennée
While writing my own VirtIO devices I've gotten confused with how things are structured and what sort of shared infrastructure there is. If we can document how everything is supposed to work we can then maybe start cleaning up inconsistencies in the code. Based-on: 20220309135355.4149689-1-alex.be