qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel@nongnu.org,  Leonardo Bras <leobras@redhat.com>,
	 Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH] multifd: Add colo support
Date: Thu, 11 May 2023 12:16:38 +0200	[thread overview]
Message-ID: <87bkir5g1l.fsf@secure.mitica> (raw)
In-Reply-To: <20230511100227.2fd1b86d@gecko.fritz.box> (Lukas Straub's message of "Thu, 11 May 2023 12:02:27 +0200")

Lukas Straub <lukasstraub2@web.de> wrote:
> On Thu, 11 May 2023 11:52:55 +0200
> Juan Quintela <quintela@redhat.com> wrote:
>
>> Lukas Straub <lukasstraub2@web.de> wrote:
>> > On Tue,  9 May 2023 20:15:28 +0200
>> > Juan Quintela <quintela@redhat.com> wrote:
>> >  
>> >> From: Lukas Straub <lukasstraub2@web.de>
>> >> 
>> >> Like in the normal ram_load() path, put the received pages into the
>> >> colo cache and mark the pages in the bitmap so that they will be
>> >> flushed to the guest later.
>> >> 
>> >> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
>> >> 
>> >> ---
>> >> 
>> >> Hi Lukas
>> >> 
>> >> What about this instead of your other three patches?  I think it is
>> >> clearer, and I don't think that we are going to have anything else
>> >> that is going to hook there anytime soon.
>> >> 
>> >> Notice that I put CONFIG_COLO waiting for Vladimir changes to get in
>> >> before I merge this.
>> >> 
>> >> Notice also that I "lost" the line:
>> >> 
>> >>   p->host = p->block->host;
>> >> 
>> >> In the error case.  But in that case we are aborting the migration, so
>> >> we don't care.
>> >> 
>> >> Can you check if it works for you?
>> >> Here it compiles, so it must be perfect.
>> >> 
>> >> Thanks, Juan.  
>> >
>> > This way is okay for now. Though I will send a patch.  
>> 
>> 
>> If it works for you, you can add a review-by and I will integrate in
>> next PULL.
>
> Nack, There are quite few things wrong at a glance. I will cook up my
> own patch, similar to this one.

Perfect.  Thanks.
>> >> @@ -23,7 +23,7 @@ softmmu_ss.add(files(
>> >>    'migration.c',
>> >>    'multifd.c',
>> >>    'multifd-zlib.c',
>> >> -  'multifd-zlib.c',
>
> ???

Patch sent upstream to fix it.  Introduced (by me) when I rebased/merged
your compression code changes.

>> >> diff --git a/migration/multifd-colo.h b/migration/multifd-colo.h
>> >> new file mode 100644
>> >> index 0000000000..1636c617fc
>> >> --- /dev/null
>> >> +++ b/migration/multifd-colo.h
>> >> @@ -0,0 +1,24 @@
>> >> +/*
>> >> + * multifd colo header
>> >> + *
>> >> + * Copyright (c) Lukas Straub <lukasstraub2@web.de>
>> >> + *
>> >> + * This work is licensed under the terms of the GNU GPL, version 2 or later.
>> >> + * See the COPYING file in the top-level directory.
>> >> + */
>> >> +
>> >> +#ifndef QEMU_MIGRATION_MULTIFD_COLO_H
>> >> +#define QEMU_MIGRATION_MULTIFD_COLO_H
>> >> +
>> >> +#ifndef CONFIG_COLO
>
> Should be CONFIG_REPLICATION

Aha, thanks.

Will wait for your patch.

Later, Juan.

>> >> +
>> >> +void multifd_colo_prepare_recv_pages(MultiFDRecvParams *p);
>> >> +void multifd_colo_process_recv_pages(MultiFDRecvParams *p);
>> >> +
>> >> +#else
>> >> +
>> >> +static inline void multifd_colo_prepare_recv_pages(MultiFDRecvParams *p) {}
>> >> +static inline void multifd_colo_process_recv_pages(MultiFDRecvParams *p) {}
>> >> +
>> >> +#endif /* CONFIG_COLO */
>> >> +#endif  
>> 



      reply	other threads:[~2023-05-11 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 18:15 [PATCH] multifd: Add colo support Juan Quintela
2023-05-11  9:47 ` Lukas Straub
2023-05-11  9:52   ` Juan Quintela
2023-05-11 10:02     ` Lukas Straub
2023-05-11 10:16       ` Juan Quintela [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=87bkir5g1l.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=leobras@redhat.com \
    --cc=lukasstraub2@web.de \
    --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 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).