public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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

  parent reply	other threads:[~2007-06-11  8:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10  7:33 More virtio users Avi Kivity
2007-06-10  8:06 ` Muli Ben-Yehuda
2007-06-10  8:09   ` Avi Kivity
2007-06-12 22:07     ` [kvm-devel] [Xen-devel] " Arnd Bergmann
2007-06-12 23:40       ` [kvm-devel] " Caitlin Bestler
2007-06-12 23:54         ` [kvm-devel] [Xen-devel] " Arnd Bergmann
2007-06-13  5:28           ` [kvm-devel] " Muli Ben-Yehuda
2007-06-14 19:41           ` Caitlin Bestler
     [not found]             ` <1EF1E44200D82B47BD5BA61171E8CE9D04269D6E-Wx+fQJ8T8QJuheSVJXE+poKqz+Jmtwh+qs7JOtOhHmkAvxtiuMwx3w@public.gmane.org>
2007-06-14 23:39               ` [Xen-devel] " Arnd Bergmann
     [not found]                 ` <200706150139.36770.arnd-r2nGTMty4D4@public.gmane.org>
2007-06-15 16:26                   ` Caitlin Bestler
2007-06-10  8:13 ` Rusty Russell
2007-06-10  8:16   ` Avi Kivity
2007-06-10 12:37     ` Rusty Russell
2007-06-11  6:41       ` Jens Axboe
2007-06-11  7:29         ` Rusty Russell
2007-06-11  7:33           ` Jens Axboe
2007-06-12  0:31             ` Rusty Russell
2007-06-12  6:24               ` Jens Axboe
2007-06-12  7:52                 ` Rusty Russell
2007-06-12  7:56                   ` Jens Axboe
2007-06-11  8:16   ` Gerd Hoffmann [this message]
2007-06-11  8:19     ` Avi Kivity
2007-06-11 19:24     ` Anthony Liguori
2007-06-11 23:19     ` Rusty Russell
2007-06-12  0:47       ` [Xen-devel] " Benjamin Herrenschmidt
     [not found]     ` <1181603983.16428.100.camel__36651.2330751449$1181608748$gmane$org@localhost.localdomain>
2007-06-12  3:36       ` Anthony Liguori
2007-06-12  4:07         ` [Xen-devel] " Benjamin Herrenschmidt
2007-06-11 13:44   ` Markus Armbruster
2007-06-11  3:04 ` ron minnich
2007-06-12 22:01 ` [kvm-devel] " Arnd Bergmann
     [not found]   ` <200706130001.21431.arnd-r2nGTMty4D4@public.gmane.org>
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