[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [v4][PATCH 11/19] tools: introduce some new parameters to set rdm policy
On Fri, Jun 26, 2015 at 05:36:19PM +0800, Chen, Tiejun wrote: > >>TODO: in the future this parameter may be further extended to allow > >>specifying arbitrary regions, e.g. even those belonging to another > >>platform as a preparation for live migration with passthrough devices. > > > >I don't think this needs to be explained in this document at all. > >Whenever someone does that work they can update the docs to describe the > >new functionality. > > Okay. > > > > >> > >>... > >> > >>> > >>>>+ > >>>>+"none" means we have nothing to do all reserved regions and ignore all > >>>>policies, > > [snip] > > >>Just let me rephrase this, > >> > >>"none" means we don't check any reserved regions and then all rdm > >>policies would be ignored, so guest just work as before. > > > >When or why would I write: > > rdm = "none" > >in my configuration file instead of just not saying anything? > > As you know we just have two options, "none" vs. "host". So we need a > explicit flag as a default libxl value to work out our mechanism. > > +libxl_rdm_reserve_type = Enumeration("rdm_reserve_type", [ > + (0, "none"), > + (1, "host"), > + ]) > + > > We just think this name can make sense, right? > What Ian was getting at was specifying type=none is the same as not specifying at all. So on *xl* level we can just expose "host" as the only valid type. Ian, correct me if I misunderstand. Wei. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |