qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mrhines@linux.vnet.ibm.com
To: qemu-devel@nongnu.org
Cc: hinesmr@cn.ibm.com, "Michael R. Hines" <mrhines@us.ibm.com>,
	quintela@redhat.com
Subject: [Qemu-devel] [RFC PATCH v1 0/3] provenance: save migration stats after completion to destination
Date: Tue, 18 Feb 2014 13:53:19 +0800	[thread overview]
Message-ID: <1392702802-11592-1-git-send-email-mrhines@linux.vnet.ibm.com> (raw)

From: "Michael R. Hines" <mrhines@us.ibm.com>

This series allows us to send the contents of the entire MigrationInfo structure to the
destination once the migration is over. This is very useful for analyzing
the result of a migration, and particularly useful for management software and
policy. Normally, the information ins MigrationInfo is completely lost when
the source VM is destroyed, but with this series, we can preserve the statistics
for retrieval.

The QMP architecture has sufficient functionality to serialize and
deserialize arbitrary objects into JSON and back again (very nice).

We only store the stats from the *last* migration, but not all previous migrations,
as that could potentially get unwieldy. Thus, it's the management software's (or user's)
responsibility to retrieve the statistics before another migration occurs.

Michael R. Hines (3):
  provenance: QMP command to store MigrationInfo from JSON
  provenance: serialize MigrationInfo across the wire
  provenance: expose the serialization save/load functions for migration

 include/migration/migration.h |   8 +++
 migration.c                   | 126 ++++++++++++++++++++++++++++++++++++++++--
 qapi-schema.json              |  14 +++++
 qmp-commands.hx               |  33 +++++++++++
 vl.c                          |   2 +
 5 files changed, 178 insertions(+), 5 deletions(-)

-- 
1.8.1.2

             reply	other threads:[~2014-02-18  5:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  5:53 mrhines [this message]
2014-02-18  5:53 ` [Qemu-devel] [RFC PATCH v1 1/3] provenance: QMP command to store MigrationInfo from JSON mrhines
2014-02-18  5:53 ` [Qemu-devel] [RFC PATCH v1 2/3] provenance: serialize MigrationInfo across the wire mrhines
2014-02-18  5:53 ` [Qemu-devel] [RFC PATCH v1 3/3] provenance: expose the serialization save/load functions for migration mrhines
2014-02-18 13:40 ` [Qemu-devel] [RFC PATCH v1 0/3] provenance: save migration stats after completion to destination Eric Blake
2014-02-19  2:30   ` Michael R. Hines
2014-02-19  2:40     ` Eric Blake
2014-02-19  4:22       ` Michael R. Hines

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=1392702802-11592-1-git-send-email-mrhines@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=hinesmr@cn.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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).