WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] ioemu: drop unused 4MB video memory

To: "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] ioemu: drop unused 4MB video memory
From: "Trolle Selander" <trolle.selander@xxxxxxxxx>
Date: Mon, 14 Jul 2008 12:40:06 +0100
Cc:
Delivery-date: Mon, 14 Jul 2008 04:40:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=TELx8I3jmr+YNLX8CYqFt7FisWAJwialH9j7oxyFky8=; b=Tqx95eQDbhZ/x68MPd6QmECrVDAiTSdz6NCjas6gUqNOeqr/5QfpxVKM0bG2X4HXIK bxkxckj0KlNbLGBbyCzLuIcsD0UhzZSjEwTGf9gUn421jaBLm4OkFdxFYch4SYv79o4h Wl5w3NSxRTkxY4JUpqxi0eUHBYFvjuk17m1E4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=kvIbYSJxRGIdN/xoQDO9TRm/ECeFmjQR8u7ACSTG2vle01SKzxvoo0AZ3S0vmeQtgg 13seE0deMXpvI8p8Zrp1EssiuxRu5QoqQR1xO12iy2vvhM+3e7HQfmTt2z8kgtABb0lC 2jcT3Q8wdeFINM0RqsrJ9MBVNawqkcMJI+at4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080714110903.GI4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080714104012.GG4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C4A0EC2B.23F7B%keir.fraser@xxxxxxxxxxxxx> <20080714104933.GH4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080714110903.GI4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I believe we have this disabled currently, but there is code in upstream qemu to support higher resolutions that actually make use of more memory through stdvga + VBE bios exensions. It seems a bit counterproductive to put in a lot of work to trim this down to 4 megs now if we're eventually going to support the stdvga + VBE combo for higher resolutions. Or is this 4/8 meg allocation stricly for cirrus, and stdvga mem allocation entirely separate?

/ Trolle

On Mon, Jul 14, 2008 at 12:09 PM, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx> wrote:
Samuel Thibault, le Mon 14 Jul 2008 11:49:33 +0100, a écrit :
> Keir Fraser, le Mon 14 Jul 2008 11:42:35 +0100, a écrit :
> > On 14/7/08 11:40, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:
> >
> > >>  * What about save/restore ?
> > >
> > > Ah, right, we need a compatibility version for that, I'll work on it.
> >
> > What's the compatibility problem? Is VGA_RAM_SIZE baked into the qemu save
> > image for some reason?
>
> The video memory is currently written by qemu yes.

Actually, the problem is also that everything (including qemu's dirty
bitmap) gets initialized to 4MB before the load, and it'd be clumsy to
plumb a reallocation.  Bummer.  It'd be simpler to just go expense these
4MB.

Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel