From: Gerd Hoffmann <kraxel@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
xen-devel <xen-devel@lists.xensource.com>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [Xen-devel] Re: More virtio users
Date: Mon, 11 Jun 2007 10:16:02 +0200 [thread overview]
Message-ID: <466D04C2.8010403@redhat.com> (raw)
In-Reply-To: <1181463220.16428.24.camel@localhost.localdomain>
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.
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.
Xen has virtual framebuffer, kbd & mouse, although not (yet?) in the
paravirt_ops patch queue, so there is something you can look at ;)
cheers,
Gerd
next prev parent reply other threads:[~2007-06-11 8:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <466BA965.6050208@qumranet.com>
2007-06-10 8:06 ` [Xen-devel] More virtio users Muli Ben-Yehuda
[not found] ` <20070610080602.GD3738@rhun.haifa.ibm.com>
2007-06-10 8:09 ` Avi Kivity
[not found] ` <466BB1AF.1000601@qumranet.com>
2007-06-12 22:07 ` [kvm-devel] " Arnd Bergmann
2007-06-12 23:40 ` Caitlin Bestler
2007-06-10 8:13 ` Rusty Russell
2007-06-11 3:04 ` [Xen-devel] " ron minnich
[not found] ` <1181463220.16428.24.camel@localhost.localdomain>
2007-06-10 8:16 ` Avi Kivity
[not found] ` <466BB34B.9050105@qumranet.com>
2007-06-10 12:37 ` Rusty Russell
[not found] ` <1181479060.16428.37.camel@localhost.localdomain>
2007-06-11 6:41 ` Jens Axboe
2007-06-11 7:29 ` Rusty Russell
[not found] ` <1181546953.16428.96.camel@localhost.localdomain>
2007-06-11 7:33 ` Jens Axboe
2007-06-12 0:31 ` Rusty Russell
[not found] ` <1181608287.16428.127.camel@localhost.localdomain>
2007-06-12 6:24 ` Jens Axboe
2007-06-12 7:52 ` Rusty Russell
[not found] ` <1181634747.6237.79.camel@localhost.localdomain>
2007-06-12 7:56 ` Jens Axboe
2007-06-11 8:16 ` Gerd Hoffmann [this message]
2007-06-11 8:19 ` [Xen-devel] " Avi Kivity
2007-06-11 19:24 ` Anthony Liguori
2007-06-11 23:19 ` Rusty Russell
2007-06-12 3:36 ` Anthony Liguori
[not found] ` <466E14A6.6020400@codemonkey.ws>
2007-06-12 4:07 ` Benjamin Herrenschmidt
[not found] ` <1181603983.16428.100.camel@localhost.localdomain>
2007-06-12 0:47 ` Benjamin Herrenschmidt
2007-06-12 22:01 ` [kvm-devel] " Arnd Bergmann
2007-06-14 16:27 ` [Xen-devel] " Mark Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466D04C2.8010403@redhat.com \
--to=kraxel@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).