Public bug reported:
Hi,
Previously, the shift value used for time-stamping was constant and didn't
depend on the HW chip frequency. Change that to take the frequency into
account
and calculate the maximal value in cycles per wraparound of ten seconds.
This
time slot was chosen since it gives a good accuracy in time synchronization.
Algorithm for shift value calculation:
* Round up the maximal value in cycles to nearest power of two
* Calculate maximal multiplier by division of all 64 bits set
to above result
* Then, invert the function clocksource_khz2mult() to get the shift from
maximal mult value
below is the upstream commit that should fix the issue
commit 31c128b66e5b28f468076e4f3ca3025c35342041
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty wily xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552627
Title:
mlx4_en didn't choose time-stamping shift value according to HW
frequency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552627/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
