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

Re: [Xen-devel] [PATCH v4 3/9] xen/arm: Implement set_memory_map hypercall for arm



On Fri, 2013-11-01 at 13:51 +0400, Eugene Fedotov wrote:
> 01.11.2013 13:14, Ian Campbell ÐÐÑÐÑ:
> > On Thu, 2013-10-31 at 12:56 +0400, Eugene Fedotov wrote:
> >> Can we create new DOMCTL hypercall for get/set memory map?
> > You could but do you really need it? The guest memory map is pretty much
> > static apart from RAM size and in the next version of my "xen: arm:
> > 64-bit guest support and domU FDT autogeneration" series all the
> > relevant #defines should be available to the toolstack as well as the
> > hypervisor (and if not, we can fix that).
> >
> > Any get/set memory map calls can be deferred until there is a need for a
> > more dynamic guest layout IMHO.
> >
> > Ian.
> >
> So it is not yet upstreamed: "xen: arm: 64-bit guest support and domU 
> FDT autogeneration" ?

Not yet.

> As to current patch series, how do the hypervisor acquire RAM size (and 
> base) in current upstream? (since only toolstack knows it yet, or I 
> missed something).

The toolstack makes a hypercall, via libxc:xc_domain_setmaxmem.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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