public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Radim Krcmar <rkrcmar@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, Luiz Capitulino <lcapitulino@redhat.com>,
	Rik van Riel <riel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [patch 3/3] KVM: x86: add tracepoint to wait_lapic_expire
Date: Wed, 17 Dec 2014 16:06:04 +0100	[thread overview]
Message-ID: <20141217150600.GA31053@potion.redhat.com> (raw)
In-Reply-To: <20141216140853.767043716@redhat.com>

2014-12-16 09:08-0500, Marcelo Tosatti:
> Add tracepoint to wait_lapic_expire.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>

> +++ kvm/arch/x86/kvm/lapic.c
> @@ -1120,7 +1120,7 @@ static bool lapic_timer_int_injected(str
>  void wait_lapic_expire(struct kvm_vcpu *vcpu)
>  {
>  	struct kvm_lapic *apic = vcpu->arch.apic;
> -	u64 guest_tsc, tsc_deadline;
> +	u64 orig_guest_tsc, guest_tsc, tsc_deadline;
>  
>  	if (!kvm_vcpu_has_lapic(vcpu))
>  		return;
> @@ -1133,7 +1133,7 @@ void wait_lapic_expire(struct kvm_vcpu *
>  
>  	tsc_deadline = apic->lapic_timer.expired_tscdeadline;
>  	apic->lapic_timer.expired_tscdeadline = 0;
> -	guest_tsc = kvm_x86_ops->read_l1_tsc(vcpu, native_read_tsc());
> +	orig_guest_tsc = guest_tsc = kvm_x86_ops->read_l1_tsc(vcpu, native_read_tsc());

(We could move the tracepoint here and save orig_guest_tsc.)

>  	while (guest_tsc < tsc_deadline) {
>  		int delay = min(tsc_deadline - guest_tsc, 1000ULL);
> @@ -1141,6 +1141,8 @@ void wait_lapic_expire(struct kvm_vcpu *
>  		__delay(delay);
>  		guest_tsc = kvm_x86_ops->read_l1_tsc(vcpu, native_read_tsc());
>  	}
> +
> +	trace_kvm_wait_lapic_expire(vcpu->vcpu_id, orig_guest_tsc - tsc_deadline);
>  }
>  

  reply	other threads:[~2014-12-17 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 14:08 [patch 0/3] KVM: add option to advance tscdeadline hrtimer expiration (v5) Marcelo Tosatti
2014-12-16 14:08 ` [patch 1/3] KVM: x86: add method to test PIR bitmap vector Marcelo Tosatti
2014-12-17 14:45   ` Radim Krcmar
2014-12-16 14:08 ` [patch 2/3] KVM: x86: add option to advance tscdeadline hrtimer expiration Marcelo Tosatti
2014-12-17 14:58   ` Radim Krcmar
2014-12-17 17:41     ` Marcelo Tosatti
2014-12-17 17:48       ` Paolo Bonzini
2014-12-17 19:36       ` Radim Krcmar
2014-12-18 12:24         ` Marcelo Tosatti
2014-12-23 13:18           ` Paolo Bonzini
2014-12-16 14:08 ` [patch 3/3] KVM: x86: add tracepoint to wait_lapic_expire Marcelo Tosatti
2014-12-17 15:06   ` Radim Krcmar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-23 20:58 [patch 0/3] KVM: add option to advance tscdeadline hrtimer expiration (v6) Marcelo Tosatti
2014-12-23 20:58 ` [patch 3/3] KVM: x86: add tracepoint to wait_lapic_expire Marcelo Tosatti
2014-12-15 22:06 [patch 0/3] KVM: add option to advance tscdeadline hrtimer expiration (v4) Marcelo Tosatti
2014-12-15 22:06 ` [patch 3/3] KVM: x86: add tracepoint to wait_lapic_expire Marcelo Tosatti
2014-12-16  9:03   ` Paolo Bonzini
2014-12-16 12:15     ` Marcelo Tosatti
2014-12-16 12:19       ` 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=20141217150600.GA31053@potion.redhat.com \
    --to=rkrcmar@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lcapitulino@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=riel@redhat.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