[Xen-devel] [PATCH 00 of 26 V3] libxl: improved handling for default values in API

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

Introduce a mechanism for users of libxl to explicitly say "pick the
default for me".

To do this each field has a distinguished "init_val" and each struct
has a "_setdefault" method which sets (idempotently) the defaults for
fields which have not been set to an explicit value.

Previously I went through some contortions (with "timer_mode" in
particular but also with *_memkb fields) to try and arrange that this
distinguished value was the all zeroes bit pattern.

Instead of that pain this time I have arranged that the IDL supports
the specification the distinguished val for each type/field and we
autogenerate an _init function for each data type based on that.

For reviewer convenience I've also put the series in git (based on
IanJ's git tree at: git://xenbits.xen.org/people/iwj/xen-unstable.git
(because IanJ was the reviewer who asked for it...)

The following changes since commit e4296962b0e5d913929164b913f47fe288ab783e:

  tools/hotplug: remove 4 from default runlevel in xencommons (2012-02-20 
18:58:07 +0000)

are available in the git repository at:
  git://xenbits.xen.org/people/ianc/xen-unstable.git for-ianj/libxl

Changes since last time:

* Added two unrelated patches to remove Xen public headers from
  libxl's API to the head of the queue
* Produce _dispose and _init for all Aggregate types.
* Be more assertive about why we should drop the 8M slack on PV.
* Happens to fix stubdomains, broken by 24612:54000bca7a6a due to not
  setting the CPU affinity for the stub domain.
Changes since the time before:

* I have posted large parts of the previous series as
  * libxl: drop device_model_info
  * libxl: API updates + xl: JSON
  These have been committed thereby reducing the size of this series.
* _init function support as described above
* Dropped final patch to actually select stubdoms when possible --
  this needs more investigation/sanity checking.

This series has been lightly tested with PV domains (with and without
PVFB) and HVM domains (with and without stubdom).

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel