linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Handle forward time correction gracefully
Date: Wed, 6 Apr 2016 12:33:44 +0200	[thread overview]
Message-ID: <20160406103344.GA17975@cbox> (raw)
In-Reply-To: <1459931842-29465-1-git-send-email-marc.zyngier@arm.com>

On Wed, Apr 06, 2016 at 09:37:22AM +0100, Marc Zyngier wrote:
> On a host that runs NTP, corrections can have a direct impact on
> the background timer that we program on the behalf of a vcpu.
> 
> In particular, NTP performing a forward correction will result in
> a timer expiring sooner than expected from a guest point of view.
> Not a big deal, we kick the vcpu anyway.
> 
> But on wake-up, the vcpu thread is going to perform a check to
> find out whether or not it should block. And at that point, the
> timer check is going to say "timer has not expired yet, go back
> to sleep". This results in the timer event being lost forever.
> 
> There are multiple ways to handle this. One would be record that
> the timer has expired and let kvm_cpu_has_pending_timer return
> true in that case, but that would be fairly invasive. Another is
> to check for the "short sleep" condition in the hrtimer callback,
> and restart the timer for the remaining time when the condition
> is detected.
> 
> This patch implements the latter, with a bit of refactoring in
> order to avoid too much code duplication.
> 
> Reported-by: Alexander Graf <agraf@suse.de>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
>  virt/kvm/arm/arch_timer.c | 47 +++++++++++++++++++++++++++++++++++++----------
>  1 file changed, 37 insertions(+), 10 deletions(-)
> 
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index a9ad4fe..4d0e77a 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -98,10 +98,46 @@ static void kvm_timer_inject_irq_work(struct work_struct *work)
>  	kvm_vcpu_kick(vcpu);
>  }
>  
> +static u64 kvm_timer_compute_delta(struct kvm_vcpu *vcpu)
> +{
> +	cycle_t cval, now;
> +
> +	cval = vcpu->arch.timer_cpu.cntv_cval;
> +	now = kvm_phys_timer_read() - vcpu->kvm->arch.timer.cntvoff;
> +
> +	if (now < cval) {
> +		u64 ns;
> +
> +		ns = cyclecounter_cyc2ns(timecounter->cc,
> +					 cval - now,
> +					 timecounter->mask,
> +					 &timecounter->frac);
> +		return ns;
> +	}
> +
> +	return 0;
> +}
> +
>  static enum hrtimer_restart kvm_timer_expire(struct hrtimer *hrt)
>  {
>  	struct arch_timer_cpu *timer;
> +	struct kvm_vcpu *vcpu;
> +	u64 ns;
> +
>  	timer = container_of(hrt, struct arch_timer_cpu, timer);
> +	vcpu = container_of(timer, struct kvm_vcpu, arch.timer_cpu);
> +
> +	/*
> +	 * Check that the timer has really expired from the guest's
> +	 * PoV (NTP on the host may have forced it to expire
> +	 * early). If we should have slept longer, restart it.
> +	 */
> +	ns = kvm_timer_compute_delta(vcpu);
> +	if (unlikely(ns)) {
> +		hrtimer_forward_now(hrt, ns_to_ktime(ns));
> +		return HRTIMER_RESTART;
> +	}
> +
>  	queue_work(wqueue, &timer->expired);
>  	return HRTIMER_NORESTART;
>  }
> @@ -176,8 +212,6 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  void kvm_timer_schedule(struct kvm_vcpu *vcpu)
>  {
>  	struct arch_timer_cpu *timer = &vcpu->arch.timer_cpu;
> -	u64 ns;
> -	cycle_t cval, now;
>  
>  	BUG_ON(timer_is_armed(timer));
>  
> @@ -197,14 +231,7 @@ void kvm_timer_schedule(struct kvm_vcpu *vcpu)
>  		return;
>  
>  	/*  The timer has not yet expired, schedule a background timer */
> -	cval = timer->cntv_cval;
> -	now = kvm_phys_timer_read() - vcpu->kvm->arch.timer.cntvoff;
> -
> -	ns = cyclecounter_cyc2ns(timecounter->cc,
> -				 cval - now,
> -				 timecounter->mask,
> -				 &timecounter->frac);
> -	timer_arm(timer, ns);
> +	timer_arm(timer, kvm_timer_compute_delta(vcpu));
>  }
>  
>  void kvm_timer_unschedule(struct kvm_vcpu *vcpu)
> -- 
> 2.1.4
> 

How do you guys feel about adding this to the patch for improved sleep
at night (pun intended):

diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
index a9ad4fe..230f720 100644
--- a/virt/kvm/arm/arch_timer.c
+++ b/virt/kvm/arm/arch_timer.c
@@ -91,6 +91,8 @@ static void kvm_timer_inject_irq_work(struct work_struct *work)
 	vcpu = container_of(work, struct kvm_vcpu, arch.timer_cpu.expired);
 	vcpu->arch.timer_cpu.armed = false;
 
+	BUG_ON(!kvm_timer_should_fire(vcpu));
+
 	/*
 	 * If the vcpu is blocked we want to wake it up so that it will see
 	 * the timer has expired when entering the guest.


Otherwise:

Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>

And I can queue this with CC to stable, but I would like Alex's
tested-by if possible.

Thanks,
-Christoffer

  parent reply	other threads:[~2016-04-06 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  8:37 [PATCH] KVM: arm/arm64: Handle forward time correction gracefully Marc Zyngier
2016-04-06  9:14 ` Alexander Graf
2016-04-06  9:14 ` Alexander Graf
2016-04-06 10:33 ` Christoffer Dall [this message]
2016-04-06 10:58   ` Marc Zyngier
2016-04-11 12:09 ` Tomasz Nowicki
2016-04-17 17:40   ` Tomasz Nowicki

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=20160406103344.GA17975@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).