[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/07/2014 05:03 AM, Julien Grall wrote:
> Hello Arianna,
> On 07/03/14 08:45, Arianna Avanzini wrote:
>>> I think Arianna solution's might not work if the 1:1 mapping clash with 
>>> existing
>>> layout. I might help Arianna on this subject because it will be useful to
>>> passthrough a device to the guest.
>> Sorry for the delay and for bothering you with another question. In order to
>> ensure that the 1:1 mapping of a new range of I/O memory does not clash with 
>> the
>> existing layout, we should then check that nothing else has been mapped to 
>> that
>> address range in the domU's address space?
> I think checking is not the right solution, what will you do if the range is
> effectively clash to another one?

Right, sorry.

> On a previous mail (see
> http://lists.xenproject.org/archives/html/xen-devel/2014-03/msg00036.html), 
> Ian
> has proposed to exposed the layout of the host to the guest. That will allow 
> you
> to map the memory in 1:1.
> I will need this item for device passthrough soon. I can take care of this 
> item
> if you want.

OK, thank you again for replying and making this clear.

> Regards,

 * Arianna Avanzini
 * avanzini.arianna@xxxxxxxxx
 * 73628@xxxxxxxxxxxxxxxxxxx

Xen-devel mailing list



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