Displaying 3 results from an estimated 3 matches for "libxl_bitmap_is_full".
2012 Jul 26
3
[PATCH v8] Some automatic NUMA placement documentation
About rationale, usage and (some small bits of) API.
Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
---
Changes from v7:
* avoid referring to 4.2 release as "upcoming".
* libxl placement disabling key explicitly mentioned.
* Limit of max 16 NUMA nodes explicitly mentioned.
Changes from v6:
* text updated to
2013 Dec 01
70
[PATCH 00/13] Coverity fixes for libxl
Matthew Daley (13):
libxl: fix unsigned less-than-0 comparison in e820_sanitize
libxl: check for xc_domain_setmaxmem failure in libxl__build_pre
libxl: correct file open success check in libxl__device_pci_reset
libxl: don''t leak p in libxl__wait_for_backend
libxl: remove unsigned less-than-0 comparison
libxl: actually abort if initializing a ctx''s lock fails
libxl:
2012 Jul 04
53
[PATCH 00 of 10 v3] Automatic NUMA placement for xl
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