From: Ondrej Zajicek <santiago@crfreenet.org>
To: Alexander Graf <agraf@suse.de>
Cc: linux-fbdev-devel@lists.sourceforge.net,
qemu-devel <qemu-devel@nongnu.org>,
kvm list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [Linux-fbdev-devel] [PATCH] Add VirtIO Frame Buffer Support
Date: Tue, 3 Nov 2009 00:57:33 +0100 [thread overview]
Message-ID: <20091102235733.GB28292@localhost> (raw)
In-Reply-To: <5B01907D-86BE-4693-81BA-23CB81B8B047@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Tue, Nov 03, 2009 at 12:24:15AM +0100, Alexander Graf wrote:
>> Also, we still need to keep the local frame buffer copy in sync so we
>> can mmap and read from it, right? So it's not really worth it
>> probably...
>
> But then again we could just try to be closer to a real graphics card.
> What if we'd set up a memory region on the host that is basically our
> graphics frame buffer? For S390 we could just append the graphics memory
> to the guest's memory.
>
> We could use that as backing buffer in the qemu graphics frontend and as
> frame buffer in the Linux fbdev layer, similar to what real graphics
> cards set up.
Using shared memory pages between host and guest seems like a natural
way to implement paravirtualized graphics card. Most things are
straightforward, only a little problematic thing is when fbdev
is mmaped from guest to userspace - you have to detect writes
and notify host that it changed.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-02 23:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 22:09 [Qemu-devel] [PATCH] Add VirtIO Frame Buffer Support Alexander Graf
[not found] ` <20091102223249.GC22301@localhost>
[not found] ` <D295329B-4DE0-4935-8C6B-D45042E72826@suse.de>
2009-11-02 23:24 ` [Qemu-devel] Re: [Linux-fbdev-devel] " Alexander Graf
2009-11-02 23:57 ` Ondrej Zajicek [this message]
2009-11-02 23:59 ` Alexander Graf
2009-11-03 6:21 ` [Qemu-devel] " Avi Kivity
2009-11-03 6:22 ` Alexander Graf
2009-11-03 6:24 ` Avi Kivity
2009-11-03 6:27 ` Alexander Graf
2009-11-03 6:34 ` Avi Kivity
2009-11-03 6:39 ` Alexander Graf
2009-11-03 7:43 ` Avi Kivity
2009-11-03 7:50 ` Alexander Graf
2009-11-03 8:20 ` Avi Kivity
2009-11-03 8:26 ` Alexander Graf
2009-11-03 8:53 ` Avi Kivity
2009-11-03 15:14 ` Anthony Liguori
2009-11-03 15:57 ` Avi Kivity
2009-11-03 11:25 ` Vincent Hanquez
2009-11-03 9:38 ` Avi Kivity
2009-11-03 15:29 ` [Linux-fbdev-devel] " Ondrej Zajicek
2009-11-03 16:05 ` Avi Kivity
2009-11-03 16:53 ` Ondrej Zajicek
2009-11-03 17:33 ` Paolo Bonzini
2009-11-04 16:09 ` Vincent Hanquez
2009-11-04 16:35 ` Anthony Liguori
2009-11-05 9:04 ` Avi Kivity
2009-11-06 2:39 ` Jamie Lokier
2009-11-06 3:05 ` Anthony Liguori
2009-11-05 11:36 ` Michael S. Tsirkin
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=20091102235733.GB28292@localhost \
--to=santiago@crfreenet.org \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
/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).