Re: [Xen-devel] [PATCH RFC v2 8/9] xen/arm: Implement hypercall for dirty page tracing (shadow op)

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2013-07-11 at 14:18 +0400, Eugene Fedotov wrote:
> Hi.
> 
> > Either that or perhaps reuse the existing set memory map hypercall?
> 
> The HVM parameter is easy to implement since we have many of them unused 
> on ARM.  I'll think of reusing set_memory_map (this looks like a 
> PV-specific on x86 and compat code for x86-64)

Right, I menat to cop-opt extend it to support ARM too. The benefit is
that it gives you a complete map and not just a base. I don't know how
useful that will be in practice but it seems like it might come up.

I suppose you could push a map into an hvm param but it would not be a
very good fit for that interface.

> 
> > Actually, we should be generating the DTB based on the guest
> > configuration, rather than parsing the DTB to determine the
> > configuration IYSWIM.
> 
> Could guest's device tree generation be done automatically with some tool?

My vague plan was to link against libfdt and use that.
> 
> Best regards,
> Evgeny.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel