From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45165) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFdcq-0006sU-Dt for qemu-devel@nongnu.org; Tue, 18 Feb 2014 00:53:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFdcf-0000Ah-PD for qemu-devel@nongnu.org; Tue, 18 Feb 2014 00:53:48 -0500 Received: from e39.co.us.ibm.com ([32.97.110.160]:44911) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFdcf-000093-Hm for qemu-devel@nongnu.org; Tue, 18 Feb 2014 00:53:37 -0500 Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 17 Feb 2014 22:53:34 -0700 Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id E5EEF19D8036 for ; Mon, 17 Feb 2014 22:53:31 -0700 (MST) Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1I5rW479240842 for ; Tue, 18 Feb 2014 06:53:32 +0100 Received: from d03av02.boulder.ibm.com (localhost [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1I5rWu8020525 for ; Mon, 17 Feb 2014 22:53:32 -0700 From: mrhines@linux.vnet.ibm.com Date: Tue, 18 Feb 2014 13:53:19 +0800 Message-Id: <1392702802-11592-1-git-send-email-mrhines@linux.vnet.ibm.com> Subject: [Qemu-devel] [RFC PATCH v1 0/3] provenance: save migration stats after completion to destination List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: hinesmr@cn.ibm.com, "Michael R. Hines" , quintela@redhat.com From: "Michael R. Hines" 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