search for: elem_type

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding

...vec_class, int sub_idx, > + SubRegIndex sub_reg>: Pat< > + (sub_type (vector_extract (vec_type vec_class:$src), sub_idx)), > + (EXTRACT_SUBREG vec_class:$src, sub_reg) > +>; > + > +/* Insert element pattern */ > +class Insert_Element <ValueType elem_type, ValueType vec_type, > + RegisterClass elem_class, RegisterClass vec_class, > + int sub_idx, SubRegIndex sub_reg> : Pat < > + > + (vec_type (vector_insert (vec_type vec_class:$vec), > + (elem_type elem_class:$...

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on