From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Michael Davidson <md@google.com>,
mbligh@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clockevents: avoid unnecessary reprograming of event timer
Date: Fri, 13 Feb 2009 10:39:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0902131029330.16972@localhost.localdomain> (raw)
In-Reply-To: <20090213082223.GA4606@elte.hu>
On Fri, 13 Feb 2009, Ingo Molnar wrote:
> > + if (ktime_equal(dev->next_event, expires))
> > + return 0;
> > +
>
> Hm, given that a good high-res source has nanoseconds resolution,
> what's the chance of this optimization triggering in practice?
> Near zero i think - unless we trigger useless reprogramming without
> having added or removed any new timers - but then we should
> concentrate on analyzing the reason for that redundant reprogramming.
>
> Does it trigger often for you?
The only point where this should trigger is when we come out of C2/C3
and switch the local APIC timer back on. There we reload the
next_event which was discarded in the hardware before we entered C2/C3
and switched to the broadcast timer. So this change would prevent the
rearming of the local APIC after coming out of C2/C3 and probably give
us some new C-State related headaches.
Thanks,
tglx
next prev parent reply other threads:[~2009-02-13 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:23 [PATCH] clockevents: avoid unnecessary reprograming of event timer Michael Davidson
2009-02-13 8:22 ` Ingo Molnar
2009-02-13 9:39 ` Thomas Gleixner [this message]
2009-02-13 9:55 ` Ingo Molnar
2009-02-13 18:50 ` Michael Davidson
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=alpine.LFD.2.00.0902131029330.16972@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=md@google.com \
--cc=mingo@elte.hu \
/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