From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Problem about CPU stalling in hrtimer_intterrupts()
Date: Sat, 24 Oct 2015 18:58:18 +0900 (KST) [thread overview]
Message-ID: <alpine.DEB.2.11.1510241854410.4639@nanos> (raw)
In-Reply-To: <5628E7E9.409@huawei.com>
On Thu, 22 Oct 2015, Yang Yingliang wrote:
> But I found out when the cpu is stalling, basenow.tv64(7676664221321) is
> bigger than ktime_get().tv64(7336008904750) in hrtimer_interrupt() and
> the timer->_softexpires is 7336288000000. This makes it can not finish
> the while loop until ktime_get().tv64 arrives basenow.tv64.
>
> Is it correct that basenow bigger than ktime_get() ?
You only can compare basenow and ktime_get() for the clock monotonic
base. If you are actually observing this on clock monotonic base then
base->offset of clock monotonic is not 0, which should never happen.
Thanks,
tglx
prev parent reply other threads:[~2015-10-24 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 6:43 Problem about CPU stalling in hrtimer_intterrupts() Yang Yingliang
2015-10-22 7:43 ` Thomas Gleixner
2015-10-22 9:28 ` Ding Tianhong
2015-10-22 10:25 ` Thomas Gleixner
2015-10-22 13:43 ` Yang Yingliang
2015-10-24 9:58 ` Thomas Gleixner [this message]
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.DEB.2.11.1510241854410.4639@nanos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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