qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Izik Eidus <ieidus@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Spice and legacy VGA drivers
Date: Sat, 12 Dec 2009 13:28:18 -0600	[thread overview]
Message-ID: <4B23EED2.7080806@codemonkey.ws> (raw)
In-Reply-To: <20091212194620.726c29df@redhat.com>

Izik Eidus wrote:
> That specific area in spice will be changed very soon due to new
> requiments that the offscreens will add.
> Windows direct draw allow modifying offscreen (or even primary)
> surfaces using a pointer giving to the user, this mean we can`t know
> what parts of the surface was changed... (In some modes the primary
> screen can be changed without we know about this)
>
> We already thought about few algorithems we might want to add to spice
> to better address this "changed without notifications surfaces", But it
> is still not in a state I can confirm in what direction we will go in
> the end (We still need to test most of the cases to know what fit us
> best)
>   

Okay, I'm interested in hearing more about this as it develops.  I think 
good support for legacy modes is an important requirement.

For instance, I very often interact with VMs in text console mode.  In 
cloud deployments, it's pretty common to have minimal appliances that 
don't have a full X session.

Regards,

Anthony Liguori

  reply	other threads:[~2009-12-12 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12 15:25 [Qemu-devel] Spice and legacy VGA drivers Anthony Liguori
2009-12-12 15:33 ` [Qemu-devel] " Izik Eidus
2009-12-12 17:19   ` Anthony Liguori
2009-12-12 17:30     ` Izik Eidus
2009-12-12 17:35       ` Anthony Liguori
2009-12-12 17:46         ` Izik Eidus
2009-12-12 19:28           ` Anthony Liguori [this message]
2009-12-12 19:51             ` Izik Eidus
2009-12-12 21:31             ` Dave Airlie

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=4B23EED2.7080806@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=ieidus@redhat.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 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).