kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kvm <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: Wed, 4 Oct 2017 15:33:41 +0200	[thread overview]
Message-ID: <20171004133341.GG21107@flask> (raw)
In-Reply-To: <CANRm+Cw2ZYa-ojRPphgEqa9V9+nXMaGNUkYVHgfgo9oEJrwZnQ@mail.gmail.com>

2017-10-04 09:46+0800, Wanpeng Li:
> 2017-10-04 1:06 GMT+08:00 Radim Krčmář <rkrcmar@redhat.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].
> 
> As I replied to [v2 1/4].

Right, so we probably shouldn't disable the timer.

> >> 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)
> >> @@ -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);

Changing the timer from one-shot to periodic doesn't change the expected
expiration -- I think we could instead skip hrtimer_cancel() in
apic_update_lvtt().

  reply	other threads:[~2017-10-04 13:33 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ář
2017-10-04  1:46     ` Wanpeng Li
2017-10-04 13:33       ` Radim Krčmář [this message]
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=20171004133341.GG21107@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;
as well as URLs for NNTP newsgroup(s).