qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [PATCH v4 13/17] qcow2/overlaps: Add "memory limit reac


From: Eric Blake
Subject: Re: [Qemu-block] [PATCH v4 13/17] qcow2/overlaps: Add "memory limit reached" event
Date: Mon, 04 May 2015 13:32:09 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

On 05/04/2015 01:15 PM, Max Reitz wrote:
> Later, a mechanism to set a limit on how much memory may be used for the
> overlap prevention structures will be introduced. If that limit is about
> to be exceeded, a QMP event should be emitted. This very event is
> specified by this patch.
> 
> Signed-off-by: Max Reitz <address@hidden>
> ---
>  docs/qmp/qmp-events.txt | 28 ++++++++++++++++++++++++++++
>  qapi/event.json         | 27 +++++++++++++++++++++++++++
>  2 files changed, 55 insertions(+)

> +
> +Data:
> +- "reference": Device name if set; node name otherwise. (json-string)
> +- "start":     Offset of the range of clusters (possibly) no longer being
> +               checked for writes overlapping with existing metadata.
> +               (json-int, optional)
> +- "length":    Length of that range in bytes. (json-int, optional)
> +
> +Example:
> +
> +{ "event": "QCOW2_OVERLAP_CHECK_MEMORY_LIMIT_REACHED",
> +    "data": { "reference": "virtio0", "start": "805306368",
> +              "length": "268435456" },

s/"805306368"/805306368/ and likewise for length (a json-int does not
use quotes).

Otherwise seems okay.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]