All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 13/17] qcow2/overlaps: Add "memory limit reached" event
Date: Mon, 04 May 2015 13:32:09 -0600	[thread overview]
Message-ID: <5547C939.6040207@redhat.com> (raw)
In-Reply-To: <1430766953-6913-14-git-send-email-mreitz@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

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 <mreitz@redhat.com>
> ---
>  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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-05-04 19:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 19:15 [Qemu-devel] [PATCH v4 00/17] qcow2: Add new overlap check functions Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 01/17] " Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 02/17] qcow2: Pull up overlap check option evaluation Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 03/17] qcow2: Create metadata list Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 04/17] qcow2/overlaps: Protect image header Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 05/17] qcow2/overlaps: Protect refcount table Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 06/17] qcow2/overlaps: Protect refcount blocks Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 07/17] qcow2/overlaps: Protect active L1 table Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 08/17] qcow2/overlaps: Protect active L2 tables Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 09/17] qcow2/overlaps: Protect snapshot table Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 10/17] qcow2/overlaps: Protect inactive L1 tables Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 11/17] qcow2/overlaps: Protect inactive L2 tables Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 12/17] qcow2: Use new metadata overlap check function Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 13/17] qcow2/overlaps: Add "memory limit reached" event Max Reitz
2015-05-04 19:32   ` Eric Blake [this message]
2015-05-06 13:05     ` Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 14/17] qcow2/overlaps: Add memory usage limit Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 15/17] qcow2: Add overlap structure memory size options Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 16/17] qapi: Expose new qcow2 overlap check options Max Reitz
2015-05-04 19:39   ` Eric Blake
2015-05-06 13:20     ` Max Reitz
2015-05-04 19:15 ` [Qemu-devel] [PATCH v4 17/17] iotests: Test qcow2's overlap check memory limit Max Reitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5547C939.6040207@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.