|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [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
care.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|