[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-API] [PATCH 00 of 12] [PCR-0047] Enhances XCP guest-memory-field-checking logic so that XCP can choose the most appropriate set of constraints to apply for the current context.
[PCR-0047] Enhances guest-memory-field-checking logic so that XCP can choose
the most appropriate set of constraints to apply for the current context.
By default, XCP constrains guest memory fields according to:
static-min <= dynamic-min <= dynamic-max <= static-max.
In addition to the default behaviour, it's now possible to configure XCP to
constrain guest memory fields according to:
static-min <= dynamic-min = dynamic-max = static-max.
9 files changed, 423 insertions(+), 283 deletions(-)
ocaml/license/restrictions.ml | 384 +++++++++++++------------
ocaml/license/restrictions.mli | 34 +-
ocaml/util/ocamltest.ml | 3
ocaml/util/ocamltest.mli | 3
ocaml/util/vm_memory_constraints.ml | 114 ++++---
ocaml/xapi/quicktest_vm_memory_constraints.ml | 87 ++++-
ocaml/xapi/xapi_vm.ml | 17 -
ocaml/xapi/xapi_vm_helpers.ml | 29 -
ocaml/xapi/xapi_vm_memory_constraints.ml | 35 ++
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
- Follow-Ups:
- Re: [Xen-API] [PATCH 00 of 12] [PCR-0047] Enhances XCP guest-memory-field-checking logic so that XCP can choose the most appropriate set of constraints to apply for the current context.
- [Xen-API] [PATCH 12 of 12] Refactoring slightly the function "Restrictions.to_compact_string" for readability
- [Xen-API] [PATCH 10 of 12] [PCR0047] Adding appropriate boilerplate code for Dynamic Memory Control ("dmc") to the restrictions module
- [Xen-API] [PATCH 11 of 12] [PCR0047] Adding context-dependent behaviour to function "Xapi_vm_memory_constraints.assert_valid_for_current_context"
- [Xen-API] [PATCH 09 of 12] [PCR0047] Extending Ocamldoc and reformatting sections of code in line with our OCaml Best Practices Guide
- [Xen-API] [PATCH 06 of 12] [PCR0047] Adds unit tests for functions "VM_memory_constraints.{are_pinned, are_pinned_at_static_max, are_valid, are_valid_and_pinned_at_static_max}
- [Xen-API] [PATCH 08 of 12] [PCR0047] Replaces inline memory constraint validation code with calls to function "VM_memory_constraints.assert_valid_for_current_context"
- [Xen-API] [PATCH 01 of 12] [PCR0047] Adds missing Ocamldoc comments and reformatting code in line with our Ocaml Best Practices Guide. Also removes a few anachronistic comments
- [Xen-API] [PATCH 07 of 12] [PCR0047] Adds functions "assert_{valid, valid_and_pinned_at_static_max, valid_for_current_context}" to module "Xapi_vm_memory_constraints". By default the function "assert_valid_for_current_context" acts as an alias for function "assert_valid"
- [Xen-API] [PATCH 05 of 12] [PCR0047] Refactors the "Quicktest_vm_memory_constraints" module to use the new Ocamltest "make_function_test_case" constructor
- [Xen-API] [PATCH 02 of 12] [PCR0047] Renames function "VM_memory_constraints.valid" to "VM_memory_constraints.are_valid" in anticipation of using a common prefix for additional functions to be added in a further patch
- [Xen-API] [PATCH 03 of 12] [PCR0047] Adds the predicates "VM_memory_constraints.are_{pinned, pinned_at_static_max, valid, valid_and_pinned_at_static_max}", which take a set of memory constraints and return true if (and only if) the constraints match some condition
- [Xen-API] [PATCH 04 of 12] [PCR0047] Adds to Ocamltest a new test case constructor "make_function_test_case", useful for making a test case that tests a single function
|
