From: Alexey Galakhov <agalakhov@gmail.com>
To: J William Piggott <elseifthen@gmx.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] hwclock: flush stdout in hwclock -c
Date: Mon, 20 Apr 2015 09:28:24 +0200 [thread overview]
Message-ID: <20150420092824.13611c6b@aga-ws-01> (raw)
In-Reply-To: <5534498B.4080803@gmx.com>
Hello William,
Am Sun, 19 Apr 2015 20:34:19 -0400
schrieb J William Piggott <elseifthen@gmx.com>:
> I've been advocating for the removal of the compare function. One of
> my justifications for doing so is that it has been broken from day
> one and therefore nobody can be using for anything.
>
> So could you tell me how you are using it, and what useful purpose
> it is serving for you?
We use it in an automated test of the Linux system time on an embedded
system. Recently we fixed a kernel bug introduced by one of the 3rd
party patches that caused a huge (0.01%-0.1%) drift of the
CLOCK_REALTIME due to incorrect PLL initialization. The corresponding
test based on hwclock's compare is now added to our automated test
system. The test runs hwclock -c forever and fails if any drift
anomality is discovered.
Looks like hwclock -c works correctly at least in our case. I think it
could be rewritten using clock_gettime() instead of gettimeofday().
Regards,
Alexey
next prev parent reply other threads:[~2015-04-20 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 15:26 [PATCH] hwclock: flush stdout in hwclock -c Alexey Galakhov
2015-04-20 0:34 ` J William Piggott
2015-04-20 7:28 ` Alexey Galakhov [this message]
2015-04-21 15:19 ` J William Piggott
2015-04-21 15:50 ` Alexey Galakhov
2015-04-21 19:12 ` J William Piggott
2015-04-27 8:27 ` Karel Zak
2015-04-27 21:27 ` J William Piggott
2015-04-27 21:42 ` Alexey Galakhov
2015-04-28 6:50 ` Bernhard Voelker
2015-04-28 11:27 ` J William Piggott
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=20150420092824.13611c6b@aga-ws-01 \
--to=agalakhov@gmail.com \
--cc=elseifthen@gmx.com \
--cc=util-linux@vger.kernel.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