qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, dlaor@redhat.com, lcapitulino@redhat.com,
	avi@redhat.com, danken@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] block: wr_highest_sector blockstat
Date: Wed, 28 Apr 2010 17:56:19 +0200	[thread overview]
Message-ID: <1272470181-15846-1-git-send-email-kwolf@redhat.com> (raw)

This is the minimal high watermark implementation that is needed to allow
clients to poll the value. I hope everyone can live with this solution now.

The second patch of this series is optional. It breaks clients that consider
the user monitor a stable API. They should be using QMP, but I'm not sure if we
want to break compatibility on the user monitor today.

Kevin Wolf (2):
  block: Add wr_highest_sector blockstat
  block: Extend info blockstats monitor command

 block.c     |  103 ++++++++++++++++++++++++++++++++++++++++++++--------------
 block_int.h |    1 +
 qdict.c     |    2 +-
 3 files changed, 80 insertions(+), 26 deletions(-)

             reply	other threads:[~2010-04-28 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 15:56 Kevin Wolf [this message]
2010-04-28 15:56 ` [Qemu-devel] [PATCH 1/2] block: Add wr_highest_sector blockstat Kevin Wolf
2010-04-28 15:59   ` [Qemu-devel] " Anthony Liguori
2010-04-28 16:01   ` Anthony Liguori
2010-04-28 17:04     ` Luiz Capitulino
2010-04-28 17:47       ` Anthony Liguori
2010-04-28 20:31         ` Luiz Capitulino
2010-04-29 16:03         ` Daniel P. Berrange
2010-04-29  9:48     ` Kevin Wolf
2010-04-28 17:31   ` Luiz Capitulino
2010-04-29 10:00     ` Kevin Wolf
2010-04-29 17:32       ` Luiz Capitulino
2010-04-28 15:56 ` [Qemu-devel] [PATCH 2/2] block: Extend info blockstats monitor command Kevin Wolf

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=1272470181-15846-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=avi@redhat.com \
    --cc=danken@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).