search for: libxl_device_vkb

..._info->bridge = strdup("xenbr0"); +} + int libxl_device_net2_add(libxl_ctx *ctx, uint32_t domid, libxl_device_net2 *net2) { libxl__gc gc = LIBXL_INIT_GC(ctx); @@ -1449,6 +1506,12 @@ out: } /******************************************************************************/ +void libxl_device_vkb_init(libxl_device_vkb *vkb, int dev_num) +{ + memset(vkb, 0x00, sizeof(libxl_device_vkb)); + vkb->devid = dev_num; +} + int libxl_device_vkb_add(libxl_ctx *ctx, uint32_t domid, libxl_device_vkb *vkb) { libxl__gc gc = LIBXL_INIT_GC(ctx); @@ -1647,6 +1710,22 @@ out: } /***********...

This patch adds a new option for xen config files for directly mapping hardware io memory into a vm. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 013270d..428da21 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,17 @@ is given in hexadecimal and may either a span e.g.

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

...tic int device_console_val(libxl_device_console *c_val, value v) +{ + CAMLparam1(v); + + c_val->backend_domid = Int_val(Field(v, 0)); + c_val->devid = Int_val(Field(v, 1)); + c_val->constype = (Int_val(Field(v, 2))) + CONSTYPE_XENCONSOLED; + + CAMLreturn(0); +} + +static int device_vkb_val(libxl_device_vkb *c_val, value v) +{ + CAMLparam1(v); + + c_val->backend_domid = Int_val(Field(v, 0)); + c_val->devid = Int_val(Field(v, 1)); + + CAMLreturn(0); +} + +static int device_vfb_val(libxl_device_vfb *c_val, value v) +{ + CAMLparam1(v); + + c_val->backend_domid = Int_val(Field(v, 0)); + c_val-&gt...

..._device_nic *nic, abort(); } - return 0; + return libxl__resolve_domid(gc, nic->backend_domname, &nic->backend_domid); } static int libxl__device_from_nic(libxl__gc *gc, uint32_t domid, @@ -3156,7 +3165,7 @@ out: int libxl__device_vkb_setdefault(libxl__gc *gc, libxl_device_vkb *vkb) { - return 0; + return libxl__resolve_domid(gc, vkb->backend_domname, &vkb->backend_domid); } static int libxl__device_from_vkb(libxl__gc *gc, uint32_t domid, @@ -3255,7 +3264,7 @@ int libxl__device_vfb_setdefault(libxl__gc *gc, libxl_device_vfb *vfb) libxl_defbool_s...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

...RAY_SIZE(roperm)); if (!xs_transaction_end(ctx->xsh, t, 0)) if (errno == EAGAIN) goto retry_transaction; free(dmargs); + libxl_free_all(&gc); return 0; } @@ -1362,6 +1437,7 @@ static int libxl_create_stubdom(libxl_ct libxl_device_vkb *vkb, libxl_device_model_starting **starting_r) { + libxl_gc gc = LIBXL_INIT_GC(ctx); int i, num_console = 1, ret; libxl_device_console *console; libxl_domain_create_info c_info; @@ -1373,13 +1449,15 @@ static int libxl_create_stubdom(libxl_ct...

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