All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richardw.yang@linux.intel.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: quintela@redhat.com, Wei Yang <richardw.yang@linux.intel.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration/postcopy: use mis->bh instead of allocating a QEMUBH
Date: Wed, 24 Jul 2019 09:08:32 +0800	[thread overview]
Message-ID: <20190724010832.GA2199@richard> (raw)
In-Reply-To: <20190723172353.GO2719@work-vm>

On Tue, Jul 23, 2019 at 06:23:53PM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.yang@linux.intel.com) wrote:
>> For migration incoming side, it either quit in precopy or postcopy. It
>> is save to use the mis->bh for both instead of allocating a dedicated
>
>     ^^^^ 'safe' not 'save'
>

oops,  thanks for pointing out.

>> QEMUBH for postcopy.
>> 
>> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>
>Yes, I think that's OK; it's a little subtle.  Once postcopy is in 'run'
>then the main incoming code will exit before running it's bh, so you're
>right that it's free for us to use.
>
>
>Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
>> ---
>>  migration/savevm.c | 17 ++++-------------
>>  1 file changed, 4 insertions(+), 13 deletions(-)
>> 
>> diff --git a/migration/savevm.c b/migration/savevm.c
>> index 25fe7ea05a..0105068579 100644
>> --- a/migration/savevm.c
>> +++ b/migration/savevm.c
>> @@ -1856,16 +1856,10 @@ static int loadvm_postcopy_handle_listen(MigrationIncomingState *mis)
>>      return 0;
>>  }
>>  
>> -
>> -typedef struct {
>> -    QEMUBH *bh;
>> -} HandleRunBhData;
>> -
>>  static void loadvm_postcopy_handle_run_bh(void *opaque)
>>  {
>>      Error *local_err = NULL;
>> -    HandleRunBhData *data = opaque;
>> -    MigrationIncomingState *mis = migration_incoming_get_current();
>> +    MigrationIncomingState *mis = opaque;
>>  
>>      /* TODO we should move all of this lot into postcopy_ram.c or a shared code
>>       * in migration.c
>> @@ -1897,8 +1891,7 @@ static void loadvm_postcopy_handle_run_bh(void *opaque)
>>          runstate_set(RUN_STATE_PAUSED);
>>      }
>>  
>> -    qemu_bh_delete(data->bh);
>> -    g_free(data);
>> +    qemu_bh_delete(mis->bh);
>>  }
>>  
>>  /* After all discards we can start running and asking for pages */
>> @@ -1906,7 +1899,6 @@ static int loadvm_postcopy_handle_run(MigrationIncomingState *mis)
>>  {
>>      PostcopyState old_ps = POSTCOPY_INCOMING_LISTENING;
>>      PostcopyState ps = postcopy_state_set(POSTCOPY_INCOMING_RUNNING, &old_ps);
>> -    HandleRunBhData *data;
>>  
>>      trace_loadvm_postcopy_handle_run();
>>      if (ps != old_ps) {
>> @@ -1914,9 +1906,8 @@ static int loadvm_postcopy_handle_run(MigrationIncomingState *mis)
>>          return -1;
>>      }
>>  
>> -    data = g_new(HandleRunBhData, 1);
>> -    data->bh = qemu_bh_new(loadvm_postcopy_handle_run_bh, data);
>> -    qemu_bh_schedule(data->bh);
>> +    mis->bh = qemu_bh_new(loadvm_postcopy_handle_run_bh, mis);
>> +    qemu_bh_schedule(mis->bh);
>>  
>>      /* We need to finish reading the stream from the package
>>       * and also stop reading anything more from the stream that loaded the
>> -- 
>> 2.17.1
>> 
>--
>Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

-- 
Wei Yang
Help you, Help me


      reply	other threads:[~2019-07-24  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20 22:39 [Qemu-devel] [PATCH] migration/postcopy: use mis->bh instead of allocating a QEMUBH Wei Yang
2019-07-23 17:23 ` Dr. David Alan Gilbert
2019-07-24  1:08   ` Wei Yang [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=20190724010832.GA2199@richard \
    --to=richardw.yang@linux.intel.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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.