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

[Xen-devel] [PATCH 0 of 4] videoram allocation and stdvga improvements

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0 of 4] videoram allocation and stdvga improvements
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Tue, 13 Jan 2009 12:17:47 +0000
Delivery-date: Tue, 13 Jan 2009 04:23:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080505)
Hi all,
now the videoram is allocated by hvmloader, that takes care of
communicating to qemu the address where the videoram is allocated,
writing to a xen_platform ioport.
The situation gets more complicated when we let the user configure the
amount of videoram to give to the guest: hvmloader has to read the
videoram size from xen_platform, allocate the videoram and write the
address back to xen_platform.
In order to simplify the codepath and the libxc API, this patch series
removes the videoram allocation code from hvmloader and lets qemu do the
job, using xc_domain_memory_populate_physmap.
After this change I ported the "stdvga improvements" patches by Trolle
to this new videoram allocation system: the changes are few, mainly to
set_vram_mapping.

The series consists of 4 patches:

PATCH 1 of 4: populate guest videoram
this patch applies to xen-unstable and removes the videoram allocation
code from hvmloader, it also moves hvmloader memory base from 0xff000000
to 0xfc000000.

PATCH 2 of 4: ioemu: populate guest videoram
this patch applies to qemu-xen-unstable and implements the new way of
populating the videoram in the guest and mapping it in qemu.
Initially the videoram is populated at the address 0xff000000 in guest
memory address space.

PATCH 3 of 4: stdvga improvements
this patch is the "stdvga improvements" patch to xen-unstable without
any change to hvmloader (they are not needed any more).
It also moves the xc_hvm_build special pages top address from 0x100000
to 0xff000, to leave more room for the videoram.

PATCH 4 of 4: ioemu: stdvga improvements
this patch is the "stdvga improvements" patch to qemu-xen-unstable with
the due changes for the new videoram allocation system.

Best Regards,

Stefano Stabellini

Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

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