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

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

On 03/03/14 19:19, Dario Faggioli wrote:
This code is common on both x86 and ARM. On x86, we don't want to map
the I/O mem region in the guest here. QEMU will do it later.

Right. I took a quick look and, as you're saying, I found the call sites
of xc_domain_memory_mapping() in QEMU's code (in _pt_iomem_helper() ).
At the same time, I see QEMU being created as a device model in this
same function, below this hunk... But that does _not_ _always_ happen, I
think, does it?

In particular, what about PV guests for which libxl__need_xenpv_qemu()
returns 0? Who calls xc_domain_memory_mapping() on the specified iomem
region(s) for them?

Only the PV guest knows its memory layout. I guess xc_domain_memory_mapping is called by itself.

Adding Tim and Jan that might be able to answer to this question.

Julien Grall

Xen-devel mailing list



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