All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Introduce "info migrate-times" monitor command
Date: Thu, 14 Jul 2011 12:15:22 +0200	[thread overview]
Message-ID: <4E1EC1BA.2010608@redhat.com> (raw)
In-Reply-To: <4E1EBF5F.5030307@redhat.com>

On 07/14/2011 12:05 PM, Michal Novotny wrote:
> What do you mean by removing migration.c from the list? Do you mean
> doing no modifications to this file?

No usage of the time variables in migration.c.

> it's about milliseconds

It's noise anyway.

> The arch_init.c to include savevm-related code doesn't make any sense in
> general which is the thing I have to agree but if we want to measure the
> ram_save_live() per each stage we need to alter the ram_save_live()
> function which is present in the arch_init.c file (this is directly in
> vl.c file for RHEL-6 version of qemu however for upstream version we
> need to modify arch_init.c to provide the most precise RAM transfer
> values per each stage). We can move the ram_save_live() function into
> some other file, like savevm.c or vl.c... Is this what you mean by "If
> you move that code back to savevm.c" ? The code is in vl.c file for
> RHEL-6, not savevm.c and I don't know whether it ever was in savevm.c .

I think savevm.c is the right place for it.

Alternatively, what about updating the information for ram and disk 
directly in qemu_savevm_state_begin/iterate/complete (and similarly for 
loading)?  Just change "disk" to "block" so that it matches the 
parameter of register_savevm_live in block-migration.c.

Paolo

  reply	other threads:[~2011-07-14 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 13:06 [Qemu-devel] [PATCH] Introduce "info migrate-times" monitor command Michal Novotny
2011-07-13 14:11 ` Paolo Bonzini
2011-07-14  8:45   ` Michal Novotny
2011-07-14  9:44     ` Paolo Bonzini
2011-07-14 10:05       ` Michal Novotny
2011-07-14 10:15         ` Paolo Bonzini [this message]
2011-07-14 10:20           ` Michal Novotny

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=4E1EC1BA.2010608@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=minovotn@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.