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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [HVM] Patches to make HVM capable of running OS/

To: Trolle Selander <trolle.selander@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [HVM] Patches to make HVM capable of running OS/2.
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 16 Mar 2007 12:21:07 +0000
Cc: Mats.Petersson@xxxxxxx, thomas.woller@xxxxxxx
Delivery-date: Fri, 16 Mar 2007 05:20:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <515922b50703160507v5da9ad6eg3389c46044a0f8d1@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdnxZKn0SSkVdO4EduhtwAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] [HVM] Patches to make HVM capable of running OS/2.
User-agent: Microsoft-Entourage/
On 16/3/07 12:07, "Trolle Selander" <trolle.selander@xxxxxxxxx> wrote:

This is a "minimally intrusive" way to fix an issue that I think should really be fixed in a different way.
Currently, the shared info, ioreq and buffered_io pages are mapped into the guest's memory space as the three highest page frames. They are "protected" from use by being marked as reserved in the e820 ram map. However, legacy software won't know about the e820 call, and since the older e801 call reports all ram, including the shared pages, the guest OS will end up using them as regular ram with disastrous results.
This patch makes the older e801 bios call report one 64kb block less memory, thus "protecting" the shared pages from older OS's in a similar manner to the e820 call, at the expense of 52kb of wasted ram (the e801 call reports memory in 64kb blocks, so no way around this).

I think we should reserve a 64kB block just below 0xF0000000 (by marking E820_RESERVED) and put these ‘special pages’ in there. The fact they’re not currently mentioned by the e820 map at all is pretty bad — an OS might decide to remap PCI devices on top of them, for example!

 -- Keir
Xen-devel mailing list