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

Re: [Xen-devel] [PATCH v8 10/13] libxl/xl: deprecate the build_info->cpumap field



On Tue, Jun 17, 2014 at 12:29:42PM +0200, Dario Faggioli wrote:
[...]
> > > diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
> > > index c087cbc..af48622 100644
> > > --- a/docs/man/xl.cfg.pod.5
> > > +++ b/docs/man/xl.cfg.pod.5
> > > @@ -143,11 +143,11 @@ Combining this with "all" is also possible, meaning 
> > > "all,^nodes:1"
> > >  results in all the vcpus of the guest running on all the cpus on the
> > >  host, except for the cpus belonging to the host NUMA node 1.
> > >  
> > > -=item ["2", "3"] (or [2, 3])
> > > +=item ["2", "3-8,^5"]
> > >  
> > 
> > What happens if I still have [2, 3] in my config? From the lexer's PoV
> > 2 and "2" are different things.
> > 
> It will continue to work. I am changing this line because I think the
> manual should advertise the "xx" syntax, which is more powerful, i.e.,
> allows ranges. In fact, while [2, 3] works, [2-3, 4-5] does not.
> 
> I really think this is fine as:
>  - existing config will continue working
>  - new configs should use "" syntax, which as said is more powerful
> 

Thanks for explanation.

Wei.

_______________________________________________
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®.