From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH v2 11/16] libxc: get and set soft and hard affinity Date: Thu, 14 Nov 2013 15:38:09 +0000 Message-ID: <5284EE61.5000707@eu.citrix.com> References: <20131113190852.18086.5437.stgit@Solace> <20131113191242.18086.73258.stgit@Solace> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20131113191242.18086.73258.stgit@Solace> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli , xen-devel@lists.xen.org Cc: Marcus Granado , Keir Fraser , Ian Campbell , Li Yechen , Andrew Cooper , Juergen Gross , Ian Jackson , Jan Beulich , Justin Weaver , Matt Wilson , Elena Ufimtseva List-Id: xen-devel@lists.xenproject.org On 13/11/13 19:12, Dario Faggioli wrote: > by using the new flag introduced in the parameters of > DOMCTL_{get,set}_vcpuaffinity. > > This happens in two new xc calls: xc_vcpu_setaffinity_hard() > and xc_vcpu_setaffinity_soft() (an in the corresponding > getters, of course). Personally I think: * You should be able to set both HARD and SOFT flags, in which case it will set both hard and soft affinities * You should expose the "flags" to the xc caller, so that the caller can set either one or both. > > The existing xc_vcpu_{set,get}affinity() call is also retained, > with the following behavior: > > * xc_vcpu_setaffinity() sets both the hard and soft affinity; > * xc_vcpu_getaffinity() gets the hard affinity. > > This is mainly for backward compatibility reasons, i.e., trying > not to break existing callers/users. The xc interface isn't stable, right? Couldn't we just change the callers (presumably just xend and libxl)? -George