All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	quintela@redhat.com
Subject: Re: [Qemu-devel] VM-Migration
Date: Wed, 26 Apr 2017 17:14:40 +0100	[thread overview]
Message-ID: <20170426161439.GG2098@work-vm> (raw)
In-Reply-To: <CAJ2SuL=qbGqwt0JCLOLZ41fLTLwKDb0KjDANLTBTb7uLK+5m-w@mail.gmail.com>

* Pradeep Kiruvale (pradeepkiruvale@gmail.com) wrote:
> Hi All,
> 
> Is it possible to enable/disable to migration features on the fly for a
> qemu VM?
> I mean through qmp interface kind of a interface?
> 
> I am asking this because keeping the dirty memory list, this could consume
> some
> compute and memory. So, the plan is to enable when the VM needs to be
> migrated.
> 
> Please clarify.

These bitmaps should already only be allocated during the migration process,
so you shouldn't be seeing any overhead during normal running.

See migration/ram.c ram_save_setup->ram_state_init which allocates
ram_bitmap and that only happens at the start of migration.
ram_state_init also calls memory_global_dirty_log_start which does
the kernel side of it.

Dave

> Regards,
> Pradeep
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2017-04-26 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 15:51 [Qemu-devel] VM-Migration Pradeep Kiruvale
2017-04-26 16:14 ` Dr. David Alan Gilbert [this message]
2017-04-27  9:40   ` Pradeep Kiruvale

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=20170426161439.GG2098@work-vm \
    --to=dgilbert@redhat.com \
    --cc=pradeepkiruvale@gmail.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.