All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, dgilbert@redhat.com,
	peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/5] migration: Create load_setup()/cleanup() methods
Date: Tue, 13 Jun 2017 11:57:21 +0200	[thread overview]
Message-ID: <871sqoky66.fsf@secure.mitica> (raw)
In-Reply-To: <20170608125937.GC4427@noname.redhat.com> (Kevin Wolf's message of "Thu, 8 Jun 2017 14:59:37 +0200")

Kevin Wolf <kwolf@redhat.com> wrote:
> Am 02.06.2017 um 00:15 hat Juan Quintela geschrieben:
>> We need to do things at load time.
>> 
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>>  include/migration/register.h |  2 ++
>>  migration/savevm.c           | 31 +++++++++++++++++++++++++++++++
>>  2 files changed, 33 insertions(+)
>> 
>> diff --git a/include/migration/register.h b/include/migration/register.h
>> index 8e37185..0862bb8 100644
>> --- a/include/migration/register.h
>> +++ b/include/migration/register.h
>> @@ -42,6 +42,8 @@ typedef struct SaveVMHandlers {
>>                                uint64_t *non_postcopiable_pending,
>>                                uint64_t *postcopiable_pending);
>>      LoadStateHandler *load_state;
>> +    int (*load_setup)(QEMUFile *f, void *opaque);
>> +    int (*load_cleanup)(void *opaque);
>>  } SaveVMHandlers;
>
> I see that you add code to call load_setup(), but don't you want to call
> load_cleanup() somewhere, too?

Oops, you are right.

I just sent another version of this series.  They are built on top of my
pull request.  And I added the call to load_cleanup.

Thanks for the review, Juan.

  reply	other threads:[~2017-06-13  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 22:15 [Qemu-devel] [PATCH 0/5] Create setup/cleanup methods for migration incoming side Juan Quintela
2017-06-01 22:15 ` [Qemu-devel] [PATCH 1/5] migration: Rename save_live_setup() to save_setup() Juan Quintela
2017-06-01 22:15 ` [Qemu-devel] [PATCH 2/5] migration: Rename cleanup() to save_cleanup() Juan Quintela
2017-06-01 22:15 ` [Qemu-devel] [PATCH 3/5] migration: Create load_setup()/cleanup() methods Juan Quintela
2017-06-08 12:59   ` Kevin Wolf
2017-06-13  9:57     ` Juan Quintela [this message]
2017-06-01 22:15 ` [Qemu-devel] [PATCH 4/5] migration: Convert ram to use new load_setup()/load_cleanup() Juan Quintela
2017-06-01 22:15 ` [Qemu-devel] [PATCH 5/5] migration: Make compression_threads use save/load_setup/cleanup() Juan Quintela
2017-06-07 17:53 ` [Qemu-devel] [PATCH 0/5] Create setup/cleanup methods for migration incoming side Juan Quintela
2017-06-08 13:05   ` 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=871sqoky66.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.