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] Remapping memory in a HVM DomU from one pfn to another?

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Remapping memory in a HVM DomU from one pfn to another?
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 10 Jun 2008 13:15:05 +0100
Delivery-date: Tue, 10 Jun 2008 05:15:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D013DCDAC@trantor>
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: AcjKL7zJukTKL6OfRRmjF/we8x04QQAAqW7tAC/RaiAAAH1cmA==
Thread-topic: [Xen-devel] Remapping memory in a HVM DomU from one pfn to another?
User-agent: Microsoft-Entourage/11.4.0.080122
On 10/6/08 13:02, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> XENMEM_exchange. Look at 'struct xen_memory_exchange' in
>> xen/include/public/memory.h. Note that GMFN means PFN for an HVM
> guest.
>> Hopefully it is all self-explanatory enough.
>> 
> 
> I tried it and 'xm dmesg' says:
> 
> (XEN) hvm.c:747:d11 memory_op 11.
> 
> And looking in hvm.c, it appears that this occurs in
> do_memory_op_compat32(...) and the only supported memory_op function is
> XENMEM_add_to_physmap. Does that mean I'm out of luck?

It does for now. We should be using the existing PV 32-on-64 compat shim for
memory_op() hypercall for HVM 32-on-64 too. As soon as someone does that
work, this hypercall will be available to you. It would already work for HVM
64-on-64 or 32-on-32.

 -- Keir



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