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: Trolle Selander <trolle.selander@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] ioemu: drop unused 4MB video memory
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Mon, 14 Jul 2008 12:46:02 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 14 Jul 2008 04:46:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <515922b50807140440y2219ac9ek29ec6be7f83a3739@xxxxxxxxxxxxxx>
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>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Trolle Selander <trolle.selander@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20080714104012.GG4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C4A0EC2B.23F7B%keir.fraser@xxxxxxxxxxxxx> <20080714104933.GH4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080714110903.GI4466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <515922b50807140440y2219ac9ek29ec6be7f83a3739@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Trolle Selander, le Mon 14 Jul 2008 12:40:06 +0100, a écrit :
> 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.

Agreed.

> Or is this 4/8 meg allocation stricly for cirrus, and stdvga mem
> allocation entirely separate?

These allocations are independent, but are working the same way.

Samuel

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