On Tue, Feb 14, 2017 at 10:29 AM, Wei Liu <wei.l...@citrix.com> wrote: > On Thu, Feb 09, 2017 at 11:35:16AM +0000, George Dunlap wrote: >> No. This is why I'm bothering to paint this bikeshed: In every context >> *except* "cpupool create", 0 means cpupool0 -- the one that was created >> at boot, which always contains dom0, and which cannot be destroyed. >> (You can only remove all but one of the cpus.) If you remove a cpupool >> from poolid 0, you remove it from cpupool0, not "any" pool. If you >> create a domain and ask to put it in poolid 0, it will be put in >> cpupool0, not "any" pool. The only context in which "0" currently means >> "any" is when you're creating a cpupool. >> > > OK. This makes sense. > [snip] >> > I want to reserve the possibility to change that into an enum in the >> > future. >> >> Yes, I had thought of that -- but like I said, I thought enums were >> meant mostly for things for which there was an exhaustive list. In this >> case it's a "magic" value for a parameter which normally has a plain >> numerical meaning. >> >> But I can add the #define if you wish. >> > > You don't need to do that.
Is that an Ack? :-) -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
