Re: Re: More virtio users

[Avi Kivity <avi@qumranet.com>]

Gerd Hoffmann wrote:
>   Hi,
>
>> Framebuffer is an interesting one.  Virtio doesn't assume shared memory,
>> so naively the fb you would just send outbufs describing changed memory.
>> This would work, but describing rectangles is better.  A helper might be
>> the right approach here
>
> Rectangles work just fine for a framebuffer console.  They stop 
> working once you plan to run any graphical stuff such as an X-Server 
> on top of the framebuffer.  Only way to get notified about changes is 
> page faults, i.e. 4k granularity on the linear framebuffer memory.
>

For X an accelerated device is probably much better than a dumb framebuffer.

> Related to Framebuffer is virtual keyboard and virtual mouse (or 
> better touchscreen), which probably works perfectly fine with virtio.  
> I'd guess you can even reuse the input layer event struct for the 
> virtio events.

Need to be careful if we want to support non-Linux guests.


-- 
error compiling committee.c: too many arguments to function