From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NJXdm-0007RZ-NI
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:28:30 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NJXdh-0007Op-Cv
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:28:29 -0500
Received: from [199.232.76.173] (port=36945 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NJXdh-0007Ok-2P
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:28:25 -0500
Received: from mail-yw0-f171.google.com ([209.85.211.171]:46709)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NJXdh-0003dv-3m
	for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:28:25 -0500
Received: by ywh1 with SMTP id 1so1825022ywh.18
	for <qemu-devel@nongnu.org>; Sat, 12 Dec 2009 11:28:21 -0800 (PST)
Message-ID: <4B23EED2.7080806@codemonkey.ws>
Date: Sat, 12 Dec 2009 13:28:18 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Spice and legacy VGA drivers
References: <4B23B5CC.5070309@codemonkey.ws>	<20091212173315.4823f958@redhat.com>	<4B23D097.7020603@codemonkey.ws>	<20091212193025.743910b7@redhat.com>	<4B23D45C.9050008@codemonkey.ws>
	<20091212194620.726c29df@redhat.com>
In-Reply-To: <20091212194620.726c29df@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Izik Eidus <ieidus@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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