From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: HRTimer causing rtctest to fail
Date: Wed, 28 Feb 2018 14:02:20 +0200 [thread overview]
Message-ID: <87h8q15nlf.fsf@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1802281246420.1886@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Hi,
Thomas Gleixner <tglx@linutronix.de> writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner <tglx@linutronix.de> writes:
>> > All numbers in micro seconds! What happens if you load the system or
>> > restrict C-States?
>>
>> added intel_idle.max_cstate=0 to cmdline. Still see some failures,
>> albeit a lot more rare, for example, caught one on iteration 8 of
>> 8192Hz:
>>
>> 8192Hz: 1 2 3 4 5 6 7
>> PIE delta error: 0.000135 should be close to 0.000122
>>
>> That is, however, only 13 uS late. Is that within the limits of "we
>> don't quite care"?
>
> I think so. 13us (depending on the machine) can easily happen if multiple
> interrupts/timers happen at the same time or if something keeps interrupts
> disabled for a few microseconds which is certainly possible.
>
> What kind of system is this?
4 core Kabylake.
>> BTW, it took some effort to get that one failure. I'll leave rtctest
>> running in a long loop and try to figure out approximately how frequently
>> it fails, but it seems like it's within the realm of "don't care", would
>> you agree?
>
> Yes.
cool, thanks
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-02-28 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 13:20 HRTimer causing rtctest to fail Felipe Balbi
2018-02-27 16:11 ` Thomas Gleixner
2018-02-28 9:26 ` Felipe Balbi
2018-02-28 9:55 ` Thomas Gleixner
2018-02-28 10:55 ` Felipe Balbi
2018-02-28 11:50 ` Thomas Gleixner
2018-02-28 12:02 ` Felipe Balbi [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=87h8q15nlf.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.