xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Patch v6 02/13] tools/python: Scripts relating to migrationv2 streams
Date: Mon, 28 Jul 2014 16:38:07 +0100	[thread overview]
Message-ID: <53D66E5F.6010807@citrix.com> (raw)
In-Reply-To: <1406560803.16498.16.camel@kazak.uk.xensource.com>

On 28/07/14 16:20, Ian Campbell wrote:
> On Mon, 2014-07-07 at 18:37 +0100, Andrew Cooper wrote:
>> * format.py contains structure and constants as per the stream specificion.
>>
>> * convert-legacy-stream.py will take a legacy migration stream as an input,
>>   and produce a v2 stream as an output.
>>
>> * verify-stream-v2.py will verify a stream against the v2 specification.
>>
>> format.py lives as part of the regular xen library, while
>> convert-legacy-stream and verify-stream-v2 are installed as standalone scripts
>> into PRIVATE_BINDIR.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> CC: Ian Campbell <Ian.Campbell@citrix.com>
>> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
>>
>> ---
>> v6:
>>  * Move to be part of tools/python and installed in proper locations
>> ---
>>  tools/python/Makefile                         |    5 +
>>  tools/python/scripts/convert-legacy-stream.py |  622 +++++++++++++++++++++++++
>>  tools/python/scripts/verify-stream-v2.py      |  456 ++++++++++++++++++
>>  tools/python/setup.py                         |    1 +
>>  tools/python/xen/streamv2/format.py           |  148 ++++++
> I think you could reasonably take the xen.migration namespace for the
> library bit of this, streamv2 isn't very meaningful in the long run.

Ok

>
> Have you developed any particular unit tests for the conversion stuff as
> you've been developing this? I think we could check them in if yes, so
> long as the input dataset isn't an entire domain of course...

andrewcoop@andrewcoop:/local/xen.git$ ls -hlA tools/python/v2tests/
total 285M
-rw-rw-r-- 1 andrewcoop xendev  65M Jul 11 11:35 conv-v1-t64-hvm
-rw-rw-r-- 1 andrewcoop xendev  40M Jul 11 11:35 conv-v1-t64-pv32
-rw-rw-r-- 1 andrewcoop xendev  40M Jul 11 11:35 conv-v1-t64-pv64
-rw-rw-r-- 1 andrewcoop xendev 1.1K Jul  6 20:06 Makefile
-rw-r--r-- 1 andrewcoop xendev  65M May  6 14:09 v1-t64-hvm
-rw-r--r-- 1 andrewcoop xendev  40M May  6 14:05 v1-t64-pv32
-rw-r--r-- 1 andrewcoop xendev  40M May  6 14:04 v1-t64-pv64

They are the smallest domains I could create and suspend, but are still
too large to reasonably be committed

I will see if I can come up with something smaller which can be
committed, but nothing comes immediately to mind.

>
>> +        elif marker == -1: # XC_SAVE_ID_ENABLE_VERIFY_MODE
> You could define names for all these.

I considered that, but they are used exactly once, and commented in
place.  I decided that, on balance, it was better without.

>
> I'm not really enough of a Pythonista to make any particularly
> insightful review comments, but it all looks fine to me.
>
>> +squahsed_page_data_records = 0
> "squashed" (repeatedly)
>
> Ian.
>

Oops.

~Andrew

  reply	other threads:[~2014-07-28 15:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 17:37 [PATCH v6 0/13] Migration Stream v2 Andrew Cooper
2014-07-07 17:37 ` [Patch v6 01/13] docs: libxc migration stream specification Andrew Cooper
2014-07-08  3:53   ` Hongyang Yang
2014-07-08  8:48     ` Andrew Cooper
2014-07-08  8:59       ` Hongyang Yang
2014-07-08  9:36   ` David Vrabel
2014-07-08 10:48     ` Andrew Cooper
2014-07-07 17:37 ` [Patch v6 02/13] tools/python: Scripts relating to migrationv2 streams Andrew Cooper
2014-07-28 15:20   ` Ian Campbell
2014-07-28 15:38     ` Andrew Cooper [this message]
2014-07-28 15:58       ` Ian Campbell
2014-07-29 13:55         ` Jon Ludlam
2014-07-07 17:37 ` [Patch v6 03/13] [HACK] tools/libxc: save/restore v2 framework Andrew Cooper
2014-07-07 17:37 ` [Patch v6 04/13] tools/libxc: C implementation of stream format Andrew Cooper
2014-07-07 17:37 ` [Patch v6 05/13] tools/libxc: noarch common code Andrew Cooper
2014-07-07 17:37 ` [Patch v6 06/13] tools/libxc: x86 " Andrew Cooper
2014-07-07 17:37 ` [Patch v6 07/13] tools/libxc: x86 PV " Andrew Cooper
2014-07-07 17:37 ` [Patch v6 08/13] tools/libxc: x86 PV save code Andrew Cooper
2014-07-07 17:37 ` [Patch v6 09/13] tools/libxc: x86 PV restore code Andrew Cooper
2014-07-07 17:37 ` [Patch v6 10/13] tools/libxc: x86 HVM save code Andrew Cooper
2014-07-07 17:38 ` [Patch v6 11/13] tools/libxc: x86 HVM restore code Andrew Cooper
2014-07-18 14:38   ` Wen Congyang
2014-07-18 15:09     ` Andrew Cooper
2014-07-18 15:42       ` Paul Durrant
2014-07-18 16:13         ` Wen Congyang
2014-07-07 17:38 ` [Patch v6 12/13] tools/libxc: noarch save code Andrew Cooper
2014-07-07 17:38 ` [Patch v6 13/13] tools/libxc: noarch restore code Andrew Cooper
2014-07-08 10:50 ` [PATCH v6 0/13] Migration Stream v2 David Vrabel
2014-07-08 11:10   ` Ian Campbell
2014-07-08 16:35 ` Konrad Rzeszutek Wilk
2014-07-08 17:35   ` Andrew Cooper
2014-07-09  6:01     ` Hongyang Yang
2014-07-09  9:40       ` Andrew Cooper
2014-07-09 15:27         ` Konrad Rzeszutek Wilk
2014-07-10 10:19           ` Andrew Cooper
2014-07-28 15:01 ` Ian Campbell
2014-07-28 15:02   ` Andrew Cooper
2014-07-28 15:20     ` Ian Campbell

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=53D66E5F.6010807@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).