qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Liang Li <liang.z.li@intel.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, mst@redhat.com, mtosatti@redhat.com,
	quintela@redhat.com, m.gibula@beyond.pl, amit.shah@redhat.com,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [v2 0/2] Optimize the env->tsc update operation
Date: Thu, 5 Nov 2015 11:28:39 +0100	[thread overview]
Message-ID: <563B2F57.8010904@redhat.com> (raw)
In-Reply-To: <1446695464-27116-1-git-send-email-liang.z.li@intel.com>



On 05/11/2015 04:51, Liang Li wrote:
> This patch set aims for reducing the live migration downtime. It
> updates the env->tsc when stopping kvmclock with a new function.
> Rather than using 'cpu_synchronize_all_states()', which updates the
> whole CPU context just for updating the env->tsc.
> 
> For a VM with 4 CPUs, this patch set can help to reduce the VM downtime
> about 100us.
> 
> Changes in v2:
>   * Simplify 'kvm_get_tsc()' function.
>   * Introduce a new function 'kvm_synchronize_all_tsc()'
> 
> Liang Li (2):
>   kvmclock: add a new function to update env->tsc.
>   Revert "Introduce cpu_clean_all_dirty"
> 
>  cpus.c                 |  9 ---------
>  hw/i386/kvm/clock.c    | 18 ++----------------
>  include/sysemu/cpus.h  |  1 -
>  include/sysemu/kvm.h   |  8 --------
>  kvm-all.c              |  5 -----
>  target-i386/kvm.c      | 45 +++++++++++++++++++++++++++++++++++++++++++++
>  target-i386/kvm_i386.h |  1 +
>  7 files changed, 48 insertions(+), 39 deletions(-)
> 

Nice, I've applied these patches.

Paolo

      parent reply	other threads:[~2015-11-05 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  3:51 [Qemu-devel] [v2 0/2] Optimize the env->tsc update operation Liang Li
2015-11-05  3:51 ` [Qemu-devel] [v2 1/2] kvmclock: add a new function to update env->tsc Liang Li
2015-11-05  3:51 ` [Qemu-devel] [v2 2/2] Revert "Introduce cpu_clean_all_dirty" Liang Li
2015-11-05 10:28 ` Paolo Bonzini [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=563B2F57.8010904@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=m.gibula@beyond.pl \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rth@twiddle.net \
    /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).