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

Re: [Xen-devel] (v2) Design proposal for RMRR fix

> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Thursday, January 15, 2015 6:06 PM
> > The composed reserved region list is then passed to domain builder,
> > which tries to detect and avoid conflicts when populating guest RAM.
> > To avoid breaking lowmem/highmem layout, we can define a
> > lowmem_guard so if making hole for a region would make lowmem_top
> > below lowmem_guard we'll treat this region as a conflict. We may
> > either just hardcode the value like 2G (or other reasonable value in your
> > mind), or allow user to config e.g.:
> >     rmrr = [ 'host, check=force/try', 'lowmem_boundary=2G' ]
> To me it looks like lowmem_boundary makes sense only when
> check=try.

yes it only makes sense when check=try but the setting should be global
i.e. we don't want to have it configured per-device, right? do you have
a thought on a better option here?

> >
> > If above high level flow can be agreed, then we can move forward to
> > discuss next level detail e.g. how to pass the rmrr list cross different
> > components. :-)
> Apart from the minor detail mentioned I think the above is a good
> representation of what we want/need.

Thanks for your valuable inputs.

Xen-devel mailing list



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