|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-api
Re: [Xen-API] [PATCH 00 of 12] [PCR-0047] Enhances	XCP	guest-memory-fiel
 
Hi Dave, Alex
Looking at CA-37553.
 This bug seems to imply that the changes to restrict DMC to the 
Esentials edition were not successful.
 I'm wondering if something has gone wrong with applying these 
patches to trunk?
 After a bit of digging, I noticed that only two patches from 
this patch series were applied, namely patches 9 and 10, out
of an original 12 patches.
On 01/02/10 16:32, Jonathan Knowles wrote:
 
[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.
 
 
The rest of the patches remain in the xen-api.pq.hg patch
queue.
Alex - could you check whether XenRT is testing builds that
include the patches in xen-api.pq.hg?
Cheers
Jonathan
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- [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, (continued)
- [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, Jonathan Knowles
 
- [Xen-API] [PATCH 05 of 12] [PCR0047] Refactors the	"Quicktest_vm_memory_constraints" module to use the new	Ocamltest "make_function_test_case" constructor, Jonathan Knowles
 
- [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", Jonathan Knowles
 
- [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, Jonathan Knowles
 
- [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", Jonathan Knowles
 
- [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}, Jonathan Knowles
 
- [Xen-API] [PATCH 09 of 12] [PCR0047] Extending Ocamldoc and	reformatting	sections of code in line with our OCaml Best Practices Guide, Jonathan Knowles
 
- [Xen-API] [PATCH 11 of 12] [PCR0047] Adding context-dependent	behaviour to function	"Xapi_vm_memory_constraints.assert_valid_for_current_context", Jonathan Knowles
 
- [Xen-API] [PATCH 10 of 12] [PCR0047] Adding appropriate boilerplate	code for Dynamic Memory Control ("dmc") to the restrictions module, Jonathan Knowles
 
- [Xen-API] [PATCH 12 of 12] Refactoring slightly the function	"Restrictions.to_compact_string" for readability, Jonathan Knowles
 
- 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.,
Jonathan Knowles <=
 
 
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |