future plans for libxl?

[Andre Przywara <andre.przywara@amd.com>]

Hi,

what is the current master plan for libxl?
Currently I see that many features already implemented in Python are 
again implemented in libxl (migration, CPU affinity).
Are the Python tools going to be replaced at some point in the future or 
are they just reimplemented to be based upon libxl? For the NUMA guest 
effort I would like to get some ideas on how to handle tool chain 
implementation.
Or is it intended to have both these implementations in parallel (which 
would be kind of unfortunate)?
And how does this affect xend? I see that in opposite to xm some 
functionality of the xl tool works without having xend running (which I 
find very handy, cause I spent countless hours during development to 
just fix some weird xend issues just for calling xm info or xm vcpu-list).
Was there a mail or a document I missed already explaining this?

Thanks!
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632