From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Cleber Rosa <crosa@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/1] savevm/loadvm with postcopy flag qemu-iotest
Date: Mon, 15 Jan 2018 07:46:41 -0200 [thread overview]
Message-ID: <06809f02-dd3a-bbf8-cec1-016367e01e71@linux.vnet.ibm.com> (raw)
In-Reply-To: <34e2e5fd-ed31-ebcd-e610-10ef62557aca@linux.vnet.ibm.com>
Ping
On 01/02/2018 11:04 AM, Daniel Henrique Barboza wrote:
> Hi there,
>
> I saw that new iotests were added upstream and decided to re-sent this
> patch, but
> then I noticed that the files being created by this patch (201 and
> 201.out) weren't
> created upstream - we have 200 and then 202 and 203.
>
> Is this patch queued somewhere to be added or should I re-send it anyway?
>
>
> Thanks,
>
>
> Daniel
>
>
> On 12/05/2017 11:35 AM, Daniel Henrique Barboza wrote:
>> Changes from v4:
>> - added a 'refcount_bits=1' constraint for internal snapshots
>>
>> Changes from v3:
>> - rebased with master - file name changed from 198 to 201
>> - removed Creator/owner information (it can be retrieved with git)
>> - added a migration successful check before executing savevm
>> - removed a trailing double comma in the snapshot name
>>
>> Daniel Henrique Barboza (1):
>> tests/qemu-iotests: adding savevm/loadvm with postcopy flag test
>>
>> tests/qemu-iotests/201 | 120
>> +++++++++++++++++++++++++++++++++++++++++++++
>> tests/qemu-iotests/201.out | 23 +++++++++
>> tests/qemu-iotests/group | 1 +
>> 3 files changed, 144 insertions(+)
>> create mode 100755 tests/qemu-iotests/201
>> create mode 100644 tests/qemu-iotests/201.out
>>
>
>
prev parent reply other threads:[~2018-01-15 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 13:35 [Qemu-devel] [PATCH v5 0/1] savevm/loadvm with postcopy flag qemu-iotest Daniel Henrique Barboza
2017-12-05 13:35 ` [Qemu-devel] [PATCH v5 1/1] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test Daniel Henrique Barboza
2018-01-15 14:18 ` Kevin Wolf
2018-01-02 13:04 ` [Qemu-devel] [PATCH v5 0/1] savevm/loadvm with postcopy flag qemu-iotest Daniel Henrique Barboza
2018-01-15 9:46 ` Daniel Henrique Barboza [this message]
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=06809f02-dd3a-bbf8-cec1-016367e01e71@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=crosa@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).