Re: [RFC PATCH v2 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall

[Julien Grall <julien.grall@linaro.org>]

On 13/03/14 18:37, Dario Faggioli wrote:
> I thought about that too. The reason why this was the taken approach is
> this xen-devel discussion:
> http://lists.xen.org/archives/html/xen-devel/2013-06/msg00870.html
>
> in particular, this Julien's message:
> http://lists.xen.org/archives/html/xen-devel/2013-06/msg00902.html

I was a newbie when I wrote this mail ;).

IMHO, I think we will have to implement a similar solution when the 
passthrough via device tree will be handled.
But ... for the "iomem", the best solution seems to let the guest mapped 
itself the range (see my previous comment on the thread).

> One thing I don't see right now is, in the in-kernel case, what we
> should do when finding the "iomem=[]" option in a config file.

Keep the current behavior in libxl. E.g give the permission to map the 
I/O range.

> Also, just trying to recap, for Arianna's sake, moving the
> implementation of the DOMCTL in common code (and implementing the
> missing bits to make it works properly, of course) is still something we
> want, right?

I think yes.

Regards,

-- 
Julien Grall