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] How to use a machine page in Xen?

To: frank panda <pacificbigpanda@xxxxxxxxx>
Subject: Re: [Xen-devel] How to use a machine page in Xen?
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 29 Sep 2010 08:58:39 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 29 Sep 2010 09:00:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinc1UH0c0jeQFbzYF9PdsOG8WR_dLC1RiRb3X-p@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>
References: <AANLkTinc1UH0c0jeQFbzYF9PdsOG8WR_dLC1RiRb3X-p@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4
 On 09/29/2010 07:17 AM, frank panda wrote:
> Hi! Everyone.
> Xen hypervisor has 64MB protected memory.But I want to know that how
> to use these machine pages.
> Are there some APIs or routines to handle the allocation and clean of
> these page?
>

Xen reserves some memory for its own use, and that isn't generally
accessible outside of the hypervisor itself.

What are are you trying to achieve?

    J

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

<Prev in Thread] Current Thread [Next in Thread>