From: Andrey Smetanin <asmetanin@virtuozzo.com>
To: Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>
Cc: Gleb Natapov <gleb@kernel.org>,
Roman Kagan <rkagan@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 2/6] kvm/x86: Hyper-V unify stimer_start() and stimer_restart()
Date: Fri, 8 Jan 2016 00:02:04 +0300 [thread overview]
Message-ID: <568ED24C.50301@virtuozzo.com> (raw)
In-Reply-To: <568E9309.8010905@redhat.com>
On 01/07/2016 07:32 PM, Paolo Bonzini wrote:
>
>
> On 23/12/2015 12:28, Andrey Smetanin wrote:
>> This will be used in future to start Hyper-V SynIC timer
>> in several places by one logic in one function.
>>
>> Signed-off-by: Andrey Smetanin <asmetanin@virtuozzo.com>
>> Reviewed-by: Roman Kagan <rkagan@virtuozzo.com>
>> CC: Gleb Natapov <gleb@kernel.org>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>> CC: Roman Kagan <rkagan@virtuozzo.com>
>> CC: Denis V. Lunev <den@openvz.org>
>> CC: qemu-devel@nongnu.org
>> ---
>> arch/x86/kvm/hyperv.c | 37 ++++++++++++++++---------------------
>> 1 file changed, 16 insertions(+), 21 deletions(-)
>>
>> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
>> index ec3a900..8623aa6 100644
>> --- a/arch/x86/kvm/hyperv.c
>> +++ b/arch/x86/kvm/hyperv.c
>> @@ -408,6 +408,7 @@ static void stimer_cleanup(struct kvm_vcpu_hv_stimer *stimer)
>> clear_bit(stimer->index,
>> vcpu_to_hv_vcpu(vcpu)->stimer_pending_bitmap);
>> stimer->msg_pending = false;
>> + stimer->exp_time = 0;
>> }
>>
>> static enum hrtimer_restart stimer_timer_callback(struct hrtimer *timer)
>> @@ -420,24 +421,6 @@ static enum hrtimer_restart stimer_timer_callback(struct hrtimer *timer)
>> return HRTIMER_NORESTART;
>> }
>>
>> -static void stimer_restart(struct kvm_vcpu_hv_stimer *stimer)
>> -{
>> - u64 time_now;
>> - ktime_t ktime_now;
>> - u64 remainder;
>> -
>> - time_now = get_time_ref_counter(stimer_to_vcpu(stimer)->kvm);
>> - ktime_now = ktime_get();
>> -
>> - div64_u64_rem(time_now - stimer->exp_time, stimer->count, &remainder);
>> - stimer->exp_time = time_now + (stimer->count - remainder);
>> -
>> - hrtimer_start(&stimer->timer,
>> - ktime_add_ns(ktime_now,
>> - 100 * (stimer->exp_time - time_now)),
>> - HRTIMER_MODE_ABS);
>> -}
>> -
>> static int stimer_start(struct kvm_vcpu_hv_stimer *stimer)
>> {
>> u64 time_now;
>> @@ -450,9 +433,21 @@ static int stimer_start(struct kvm_vcpu_hv_stimer *stimer)
>> if (stimer->count == 0)
>> return -EINVAL;
>>
>> - stimer->exp_time = time_now + stimer->count;
>> + if (stimer->exp_time) {
>> + if (time_now >= stimer->exp_time) {
>
> Just for my education, is it possible to have this function called with
> stimer->exp_time != 0 && time_now < stimer->exp_time?
I think it's possible, assume the following situation:
GUEST HOST
periodic timer setup & start start timer
timer expiration
send timer expiration message
guest is busy and .....
do not processing timer timer expiration
message for longer than timer try to send timer expiration message
period since message slot is still occupied
..... by guest set slot->msg_pending = 1
guest wake and now
processed timer message,
since slot->msg_pending = 1
do wrmsr(HV_X64_MSR_EOM)
handle HV_X64_MSR_EOM
kvm_hv_notify_acked_sint()
schedule KVM_REQ_HV_STIMER
kvm_hv_process_stimers()
exp_time != 0 && now < exp_time
....
timer expiration
In this case we just start hrtimer again with
the same(previous) target exp_time, so I do not see any side effects.
>
> Paolo
>
>> + u64 remainder;
>> +
>> + div64_u64_rem(time_now - stimer->exp_time,
>> + stimer->count, &remainder);
>> + stimer->exp_time =
>> + time_now + (stimer->count - remainder);
>> + }
>> + } else
>> + stimer->exp_time = time_now + stimer->count;
>> +
>> hrtimer_start(&stimer->timer,
>> - ktime_add_ns(ktime_now, 100 * stimer->count),
>> + ktime_add_ns(ktime_now,
>> + 100 * (stimer->exp_time - time_now)),
>> HRTIMER_MODE_ABS);
>> return 0;
>> }
>> @@ -580,7 +575,7 @@ static void stimer_expiration(struct kvm_vcpu_hv_stimer *stimer)
>> if (!(stimer->config & HV_STIMER_PERIODIC))
>> stimer->config |= ~HV_STIMER_ENABLE;
>> else
>> - stimer_restart(stimer);
>> + stimer_start(stimer);
>> }
>>
>> void kvm_hv_process_stimers(struct kvm_vcpu *vcpu)
>>
next prev parent reply other threads:[~2016-01-07 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 11:28 [PATCH v1 0/6] KVM: Hyper-V SynIC timers migration fixes Andrey Smetanin
2015-12-23 11:28 ` [PATCH v1 1/6] kvm/x86: Drop stimer_stop() function Andrey Smetanin
2015-12-23 11:28 ` [PATCH v1 2/6] kvm/x86: Hyper-V unify stimer_start() and stimer_restart() Andrey Smetanin
2016-01-07 16:32 ` Paolo Bonzini
2016-01-07 21:02 ` Andrey Smetanin [this message]
2015-12-23 11:28 ` [PATCH v1 3/6] kvm/x86: Reorg stimer_expiration() to better control timer restart Andrey Smetanin
2016-01-07 16:34 ` Paolo Bonzini
2016-01-07 20:13 ` Andrey Smetanin
2015-12-23 11:28 ` [PATCH v1 4/6] kvm/x86: Hyper-V fix SynIC timer disabling condition Andrey Smetanin
2015-12-23 11:28 ` [PATCH v1 5/6] kvm/x86: Skip SynIC vector check for QEMU side Andrey Smetanin
2015-12-23 11:28 ` [PATCH v1 6/6] kvm/x86: Update SynIC timers on guest entry only Andrey Smetanin
2016-01-07 16:38 ` [PATCH v1 0/6] KVM: Hyper-V SynIC timers migration fixes Paolo Bonzini
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=568ED24C.50301@virtuozzo.com \
--to=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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).