Messages in this thread | | | Date | Thu, 6 Sep 2018 18:34:55 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: Ensuring wall_to_monotonic is not positive breaks use case |
| |
Rick,
On Wed, 5 Sep 2018, Rick Ratzel wrote:
> We're looking for suggestions on how best to proceed with a new change > that ideally both supports the use case described above, as well as > addresses the symptoms brought up in the initial commit (negative boot > time causes get_expiry() to overflow time_t, and show_stat() uses > "unsigned long" to print negative btime). Any thoughts on this would be > greatly appreciated.
Those symptoms are just the tip of the iceberg. For sure it screws up everything around boot time and a lot of things use boottime nowadays.
So reverting this is not really an option.
Chosing a PTP grandmaster which populates random time is a really great idea. Why has this industry the tendency to turn everything into a trainwreck?
Thanks,
tglx
| |