public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Wanpeng Li <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v2 2/4] KVM: LAPIC: Keep timer running when switching between one-shot and periodic mode
Date: Tue, 3 Oct 2017 19:06:56 +0200	[thread overview]
Message-ID: <20171003170655.GB21107@flask> (raw)
In-Reply-To: <1506647099-2688-3-git-send-email-wanpeng.li@hotmail.com>

2017-09-28 18:04-0700, Wanpeng Li:
> From: Wanpeng Li <wanpeng.li@hotmail.com>
> 
> If we take TSC-deadline mode timer out of the picture, the Intel SDM
> does not say that the timer is disable when the timer mode is change,
> either from one-shot to periodic or vice versa.

I think it does, please see comment under [v2 1/4].

> After this patch, the timer is no longer disarmed on change of mode, so
> the counter (TMCCT) keeps counting down.
> 
> So what does a write to LVTT changes ? On baremetal, the change of mode
> is probably taken into account only when the counter reach 0. When this
> happen, LVTT is use to figure out if the counter should restard counting
> down from TMICT (so periodic mode) or stop counting (if one-shot mode).
> 
> This patch is based on observation of the behavior of the APIC timer on
> baremetal as well as check that they does not go against the description
> written in the Intel SDM.
> 
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
> ---
>  arch/x86/kvm/lapic.c | 40 ++++++++++++++++++++++++++++------------
>  1 file changed, 28 insertions(+), 12 deletions(-)
> 
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index a739cbb..946c11b 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -1301,7 +1301,7 @@ static void update_divide_count(struct kvm_lapic *apic)
>  				   apic->divide_count);
>  }
>  
> -static void apic_update_lvtt(struct kvm_lapic *apic)
> +static bool apic_update_lvtt(struct kvm_lapic *apic)
>  {
>  	u32 timer_mode = kvm_lapic_get_reg(apic, APIC_LVTT) &
>  			apic->lapic_timer.timer_mode_mask;
> @@ -1309,7 +1309,9 @@ static void apic_update_lvtt(struct kvm_lapic *apic)
>  	if (apic->lapic_timer.timer_mode != timer_mode) {
>  		apic->lapic_timer.timer_mode = timer_mode;
>  		hrtimer_cancel(&apic->lapic_timer.timer);
> +		return true;
>  	}
> +	return false;
>  }
>  
>  static void apic_timer_expired(struct kvm_lapic *apic)
> @@ -1430,11 +1432,12 @@ static void start_sw_period(struct kvm_lapic *apic)
>  		HRTIMER_MODE_ABS_PINNED);
>  }
>  
> -static bool set_target_expiration(struct kvm_lapic *apic)
> +static bool set_target_expiration(struct kvm_lapic *apic, bool timer_update)
>  {
> -	ktime_t now;
> -	u64 tscl = rdtsc();
> +	ktime_t now, remaining;
> +	u64 tscl = rdtsc(), delta;
>  
> +	/* Calculate the next time the timer should trigger an interrupt */
>  	now = ktime_get();
>  	apic->lapic_timer.period = (u64)kvm_lapic_get_reg(apic, APIC_TMICT)
>  		* APIC_BUS_CYCLE_NS * apic->divide_count;
> @@ -1470,9 +1473,21 @@ static bool set_target_expiration(struct kvm_lapic *apic)
>  		   ktime_to_ns(ktime_add_ns(now,
>  				apic->lapic_timer.period)));
>  
> +	if (!timer_update)
> +		delta = apic->lapic_timer.period;
> +	else {
> +		remaining = ktime_sub(apic->lapic_timer.target_expiration, now);
> +		if (ktime_to_ns(remaining) < 0)
> +			remaining = 0;
> +		delta = mod_64(ktime_to_ns(remaining), apic->lapic_timer.period);
> +	}
> +
> +	if (!delta)
> +		return false;
> +
>  	apic->lapic_timer.tscdeadline = kvm_read_l1_tsc(apic->vcpu, tscl) +
> -		nsec_to_cycles(apic->vcpu, apic->lapic_timer.period);
> -	apic->lapic_timer.target_expiration = ktime_add_ns(now, apic->lapic_timer.period);
> +		nsec_to_cycles(apic->vcpu, delta);
> +	apic->lapic_timer.target_expiration = ktime_add_ns(now, delta);
>  
>  	return true;
>  }
> @@ -1609,12 +1624,12 @@ void kvm_lapic_restart_hv_timer(struct kvm_vcpu *vcpu)
>  	restart_apic_timer(apic);
>  }
>  
> -static void start_apic_timer(struct kvm_lapic *apic)
> +static void start_apic_timer(struct kvm_lapic *apic, bool timer_update)
>  {
>  	atomic_set(&apic->lapic_timer.pending, 0);
>  
>  	if ((apic_lvtt_period(apic) || apic_lvtt_oneshot(apic))
> -	    && !set_target_expiration(apic))
> +	    && !set_target_expiration(apic, timer_update))
>  		return;
>  
>  	restart_apic_timer(apic);
> @@ -1729,7 +1744,8 @@ int kvm_lapic_reg_write(struct kvm_lapic *apic, u32 reg, u32 val)
>  			val |= APIC_LVT_MASKED;
>  		val &= (apic_lvt_mask[0] | apic->lapic_timer.timer_mode_mask);
>  		kvm_lapic_set_reg(apic, APIC_LVTT, val);
> -		apic_update_lvtt(apic);
> +		if (apic_update_lvtt(apic) && !apic_lvtt_tscdeadline(apic))
> +			start_apic_timer(apic, true);
>  		break;
>  
>  	case APIC_TMICT:
> @@ -1738,7 +1754,7 @@ int kvm_lapic_reg_write(struct kvm_lapic *apic, u32 reg, u32 val)
>  
>  		hrtimer_cancel(&apic->lapic_timer.timer);
>  		kvm_lapic_set_reg(apic, APIC_TMICT, val);
> -		start_apic_timer(apic);
> +		start_apic_timer(apic, false);
>  		break;
>  
>  	case APIC_TDCR:
> @@ -1872,7 +1888,7 @@ void kvm_set_lapic_tscdeadline_msr(struct kvm_vcpu *vcpu, u64 data)
>  
>  	hrtimer_cancel(&apic->lapic_timer.timer);
>  	apic->lapic_timer.tscdeadline = data;
> -	start_apic_timer(apic);
> +	start_apic_timer(apic, false);
>  }
>  
>  void kvm_lapic_set_tpr(struct kvm_vcpu *vcpu, unsigned long cr8)
> @@ -2238,7 +2254,7 @@ int kvm_apic_set_state(struct kvm_vcpu *vcpu, struct kvm_lapic_state *s)
>  	apic_update_lvtt(apic);
>  	apic_manage_nmi_watchdog(apic, kvm_lapic_get_reg(apic, APIC_LVT0));
>  	update_divide_count(apic);
> -	start_apic_timer(apic);
> +	start_apic_timer(apic, false);
>  	apic->irr_pending = true;
>  	apic->isr_count = vcpu->arch.apicv_active ?
>  				1 : count_vectors(apic->regs + APIC_ISR);
> -- 
> 2.7.4
> 

  reply	other threads:[~2017-10-03 17:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29  1:04 [PATCH v2 0/4] KVM: LAPIC: Rework lapic timer to behave more like real-hardware Wanpeng Li
2017-09-29  1:04 ` [PATCH v2 1/4] KVM: LAPIC: Fix lapic timer mode transition Wanpeng Li
2017-10-03 17:05   ` Radim Krčmář
2017-10-04  1:45     ` Wanpeng Li
2017-10-04 13:21       ` Radim Krčmář
2017-10-04 13:50         ` Wanpeng Li
2017-10-04 14:02           ` Wanpeng Li
2017-09-29  1:04 ` [PATCH v2 2/4] KVM: LAPIC: Keep timer running when switching between one-shot and periodic mode Wanpeng Li
2017-10-03 17:06   ` Radim Krčmář [this message]
2017-10-04  1:46     ` Wanpeng Li
2017-10-04 13:33       ` Radim Krčmář
2017-10-04 13:57         ` Wanpeng Li
2017-09-29  1:04 ` [PATCH v2 3/4] KVM: LAPIC: Apply change to TDCR right away to the timer Wanpeng Li
2017-10-03 17:28   ` Radim Krčmář
2017-10-04  1:59     ` Wanpeng Li
2017-10-04 12:43       ` Radim Krčmář
2017-09-29  1:04 ` [PATCH v2 4/4] KVM: LAPIC: Don't silently accept bad vectors Wanpeng Li
2017-10-03 17:53   ` Radim Krčmář
2017-10-04  7:56     ` Wanpeng Li
2017-10-04 12:01       ` Radim Krčmář
2017-10-04 14:16         ` Wanpeng Li
2017-10-04 14:44           ` Radim Krčmář
2017-10-13  1:17             ` Wanpeng Li
2017-10-13 17:36               ` Radim Krčmář
2017-10-13 20:31                 ` Radim Krčmář
2017-10-15  2:41                   ` Wanpeng Li
2017-10-05 10:57 ` [PATCH v2 0/4] KVM: LAPIC: Rework lapic timer to behave more like real-hardware Wanpeng Li

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=20171003170655.GB21107@flask \
    --to=rkrcmar@redhat.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=wanpeng.li@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox