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

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

On Thu, 2014-03-13 at 16:47 +0000, Julien Grall wrote:

> >> I think, for now the best solution is to expose the same memory layout
> >> as the host when iomem is set.
> >>
> > Sure, but I don't think I see any conflict between this and the approach
> > Ian proposed above. What am I missing?
> I believe, Ian was assuming that the user know the layout because this
> solution will be used to a very specific case (I think mostly when the
> device tree won't describe the hardware).

Right, my assumption was that the kernel was also compiled for the exact
hardware layout as part of some sort of embedded/appliance situation...

> I'm wondering, if we can let the kernel calling the hypercall. He knows
> what is the memory layout of the VM.

This would be somewhat analogous to what happens with an x86 PV guest.
It would have to be an physmap call or something since this domctl
wouldn't be accessible by the guest.

That makes a lot of sense actually since this domctl seems to have been
intended for use by the x86 HVM device model (qemu).

Xen-devel mailing list



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