[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v2 11/16] libxc: get and set soft and hard affinity
- To: Dario Faggioli <dario.faggioli@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
- From: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
- Date: Thu, 14 Nov 2013 15:38:09 +0000
- Cc: Marcus Granado <Marcus.Granado@xxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Li Yechen <lccycc123@xxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Justin Weaver <jtweaver@xxxxxxxxxx>, Matt Wilson <msw@xxxxxxxxxx>, Elena Ufimtseva <ufimtseva@xxxxxxxxx>
- Delivery-date: Thu, 14 Nov 2013 15:38:55 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
