On Thu, Jun 05, 2014 at 12:32:24AM +0200, Ruediger Meier wrote:
> But before doing this I have two questions.
Maybe we can remove the test at all (or use --force to enable the test). It
was always very problematic test and I have doubts it's still necessary as
relevant hwclock code is completely different and more robust now.
> 1. I wonder what is the original purpose of this test. Are we really
> testing hwclock or the kernel or hardware? I mean setting and reading
The purpose is to test how precisely is able hwclock to set HW time.
Long time ago we had problem that each iteration added extra 0.5s to
the time.
> cock 10 times ... could this really discover a bug in our hwclock code?
Yes.
> 2. Why do we _set_ the time from ntp server at the beginning? Wouldnt it
> be enough to check whether the offset to ntp is the same before and
> after the test?
Probably yes.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
