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

Re: [Xen-devel] [RFC PATCH 3/16]: PVH xen: Add PHYSDEVOP_map_iomem

>>> On 16.01.13 at 00:35, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> wrote:
> On Mon, 14 Jan 2013 11:23:42 +0000 "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> >>> On 12.01.13 at 02:32, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
>> >>> wrote:
>> > In this patch, we define PHYSDEVOP_map_iomem and add support for
>> > it. Also, XEN_DOMCTL_memory_mapping code is put into a function so
>> > it can be shared later for PVH. No change in
>> > XEN_DOMCTL_memory_mapping functionality. 
>> Is that to say that a PVH guest will need to issue this for each and
>> every MMIO range? Irrespective of being DomU or Dom0? I would
>> have expected that this could be transparent...
> Hmm.. we discussed this at xen hackathon last year.  The 
> guest maps the entire range in one shot. Doing it this way keeps
> things flexible for future if EPT size gets to be a problem.

But is this the only way to do this? I.e. is there no transparent
alternative? I hadn't been on the hackathon, so I don't know
what eventual alternative options got explored...


Xen-devel mailing list



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