[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Remapping memory in a HVM DomU from one pfn to another?

  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Fri, 13 Jun 2008 13:53:52 +0100
  • Delivery-date: Fri, 13 Jun 2008 05:54:40 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcjKL7zJukTKL6OfRRmjF/we8x04QQAAqW7tAC/RaiAAmLfrOA==
  • Thread-topic: [Xen-devel] Remapping memory in a HVM DomU from one pfn to another?

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?

Good news is this should be supported as of xen-unstable c/s 17855. The bad
news is I'm reluctant to backport for the next 3.2 release as the required
changes to 32-on-64 argument translation are rather subtle. I guess we can
see how things go in xen-unstable and backport in a while if we sufficiently

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.