qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Glauber Costa <glommer@gmail.com>, Jan Kiszka <jan.kiszka@web.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] kvmclock: clock should count only if vm is running (v2)
Date: Tue, 25 Jun 2013 15:18:15 +0300	[thread overview]
Message-ID: <20130625121815.GR18508@redhat.com> (raw)
In-Reply-To: <20130618233825.GA19042@amt.cnet>

On Tue, Jun 18, 2013 at 08:38:25PM -0300, Marcelo Tosatti wrote:
> 
> v2: remove unnecessary runstate_is_running() usage (Paolo)
> 
> --
> 
> kvmclock should not count while vm is paused, because:
> 
> 1) if the vm is paused for long periods, timekeeping
> math can overflow while converting the (large) clocksource
> delta to nanoseconds.
> 
> 2) Users rely on CLOCK_MONOTONIC to count run time, that is,
> time which OS has been in a runnable state (see CLOCK_BOOTTIME).
> 
> Change kvmclock driver so as to save clock value when vm transitions
> from runnable to stopped state, and to restore clock value from stopped
> to runnable transition.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> 
Applied, thanks.

> diff --git a/hw/i386/kvm/clock.c b/hw/i386/kvm/clock.c
> index 87d4d0f..98e5ca5 100644
> --- a/hw/i386/kvm/clock.c
> +++ b/hw/i386/kvm/clock.c
> @@ -28,38 +28,6 @@ typedef struct KVMClockState {
>      bool clock_valid;
>  } KVMClockState;
>  
> -static void kvmclock_pre_save(void *opaque)
> -{
> -    KVMClockState *s = opaque;
> -    struct kvm_clock_data data;
> -    int ret;
> -
> -    if (s->clock_valid) {
> -        return;
> -    }
> -    ret = kvm_vm_ioctl(kvm_state, KVM_GET_CLOCK, &data);
> -    if (ret < 0) {
> -        fprintf(stderr, "KVM_GET_CLOCK failed: %s\n", strerror(ret));
> -        data.clock = 0;
> -    }
> -    s->clock = data.clock;
> -    /*
> -     * If the VM is stopped, declare the clock state valid to avoid re-reading
> -     * it on next vmsave (which would return a different value). Will be reset
> -     * when the VM is continued.
> -     */
> -    s->clock_valid = !runstate_is_running();
> -}
> -
> -static int kvmclock_post_load(void *opaque, int version_id)
> -{
> -    KVMClockState *s = opaque;
> -    struct kvm_clock_data data;
> -
> -    data.clock = s->clock;
> -    data.flags = 0;
> -    return kvm_vm_ioctl(kvm_state, KVM_SET_CLOCK, &data);
> -}
>  
>  static void kvmclock_vm_state_change(void *opaque, int running,
>                                       RunState state)
> @@ -70,8 +38,18 @@ static void kvmclock_vm_state_change(void *opaque, int running,
>      int ret;
>  
>      if (running) {
> +        struct kvm_clock_data data;
> +
>          s->clock_valid = false;
>  
> +        data.clock = s->clock;
> +        data.flags = 0;
> +        ret = kvm_vm_ioctl(kvm_state, KVM_SET_CLOCK, &data);
> +        if (ret < 0) {
> +            fprintf(stderr, "KVM_SET_CLOCK failed: %s\n", strerror(ret));
> +            abort();
> +        }
> +
>          if (!cap_clock_ctrl) {
>              return;
>          }
> @@ -84,6 +62,26 @@ static void kvmclock_vm_state_change(void *opaque, int running,
>                  return;
>              }
>          }
> +    } else {
> +        struct kvm_clock_data data;
> +        int ret;
> +
> +        if (s->clock_valid) {
> +            return;
> +        }
> +        ret = kvm_vm_ioctl(kvm_state, KVM_GET_CLOCK, &data);
> +        if (ret < 0) {
> +            fprintf(stderr, "KVM_GET_CLOCK failed: %s\n", strerror(ret));
> +            abort();
> +        }
> +        s->clock = data.clock;
> +
> +        /*
> +         * If the VM is stopped, declare the clock state valid to
> +         * avoid re-reading it on next vmsave (which would return
> +         * a different value). Will be reset when the VM is continued.
> +         */
> +        s->clock_valid = true;
>      }
>  }
>  
> @@ -100,8 +98,6 @@ static const VMStateDescription kvmclock_vmsd = {
>      .version_id = 1,
>      .minimum_version_id = 1,
>      .minimum_version_id_old = 1,
> -    .pre_save = kvmclock_pre_save,
> -    .post_load = kvmclock_post_load,
>      .fields = (VMStateField[]) {
>          VMSTATE_UINT64(clock, KVMClockState),
>          VMSTATE_END_OF_LIST()
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
			Gleb.

  reply	other threads:[~2013-06-25 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08  2:00 [Qemu-devel] [PATCH] kvmclock: clock should count only if vm is running Marcelo Tosatti
2013-06-18  9:02 ` Paolo Bonzini
2013-06-18 23:20   ` Marcelo Tosatti
2013-06-18 23:38 ` [Qemu-devel] [PATCH] kvmclock: clock should count only if vm is running (v2) Marcelo Tosatti
2013-06-25 12:18   ` Gleb Natapov [this message]
2013-07-01 11:44     ` Paolo Bonzini
2013-07-01 11:53       ` Gleb Natapov

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=20130625121815.GR18508@redhat.com \
    --to=gleb@redhat.com \
    --cc=glommer@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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).