[libvirt] [PATCH 1/3] maxmem: introduces VIR_DOMAIN_MEM_MAXIMUM flag

[Hu Tao]

On Fri, Apr 08, 2011 at 02:07:27PM +0900, Taku Izumi wrote:
> 
> This patch introduces VIR_DOMAIN_MEM_MAXIMUM flag.
> 
> Signed-off-by: Taku Izumi <izumi.taku at jp.fujitsu.com>
> ---
>  include/libvirt/libvirt.h.in |    1 +
>  src/libvirt.c                |    2 ++
>  2 files changed, 3 insertions(+)
> 
> Index: libvirt/include/libvirt/libvirt.h.in
> ===================================================================
> --- libvirt.orig/include/libvirt/libvirt.h.in
> +++ libvirt/include/libvirt/libvirt.h.in
> @@ -857,6 +857,7 @@ typedef enum {
>      VIR_DOMAIN_MEM_CURRENT = 0,        /* affect current domain state */

This patch doesn't apply, the file in my git tree doesn't have the above
line. (I've double-checked and made sure I didn't make a mistake)
Would you mind to have a check on your tree?

>      VIR_DOMAIN_MEM_LIVE    = (1 << 0), /* affect active domain */
>      VIR_DOMAIN_MEM_CONFIG  = (1 << 1), /* affect next boot */
> +    VIR_DOMAIN_MEM_MAXIMUM = (1 << 2), /* affect Max rather than current */
>  } virDomainMemoryModFlags;
>  
>  
> Index: libvirt/src/libvirt.c
> ===================================================================
> --- libvirt.orig/src/libvirt.c
> +++ libvirt/src/libvirt.c
> @@ -2832,6 +2832,8 @@ error:
>   * (that is, @flags is VIR_DOMAIN_MEM_CURRENT), then an inactive domain
>   * modifies persistent setup, while an active domain is hypervisor-dependent
>   * on whether just live or both live and persistent state is changed.
> + * If VIR_DOMAIN_MEM_MAXIMUM is set, the change affects domain's maximum memory
> + * size rather than current memory size.
>   * Not all hypervisors can support all flag combinations.
>   *
>   * Returns 0 in case of success, -1 in case of failure.
> 
> --
> libvir-list mailing list
> libvir-list at redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list