From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3 of 6] vga shared buffer
Date: Mon, 15 Sep 2008 17:47:00 +0100 [thread overview]
Message-ID: <48CE9184.2040805@eu.citrix.com> (raw)
In-Reply-To: <48CE8819.8070204@codemonkey.ws>
Anthony Liguori wrote:
> Stefano Stabellini wrote:
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>
>
> I need to carve out some time to test this series and think about
> whether it can be done without adding a new DisplayState hook. I should
> be able to respond or apply within a few days.
>
> I'm concerned about the complexity this adds to back-ends. It's not
> clear to me whether the performance justifies the added complexity.
>
The shared buffer support is completely optional, so not all the
back-ends have to support it.
Regarding the performances, keep also in mind the memory savings :)
next prev parent reply other threads:[~2008-09-15 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 11:26 [Qemu-devel] [PATCH 3 of 6] vga shared buffer Stefano Stabellini
2008-09-15 16:06 ` Anthony Liguori
2008-09-15 16:47 ` Stefano Stabellini [this message]
2008-09-24 3:00 ` andrzej zaborowski
2008-09-24 3:25 ` Anthony Liguori
2008-09-24 10:53 ` Stefano Stabellini
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=48CE9184.2040805@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.