On 08/01/2011 05:22 PM, Anthony Liguori wrote:
The char layer is confusing. There is a front-end, typically a device, that
can send and receive data. The front-end sends data by calling
qemu_chr_write().
The back-end, typically created via -chardev, can also send and receive data.
Oddly, it sends data by calling qemu_chr_read().
Let's be explicit about which function is for which party.
A different way to accomplish this would be to have each pipe expose two
interfaces (a front end and a back end), and use the same functions for
both. Just like a unix pipe.
The back end interface would typically be an internal object.
--
error compiling committee.c: too many arguments to function
