On Tue, May 09, 2023 at 02:02:05PM +0200, Andrew Zaborowski wrote: > Per https://www.kernel.org/doc/Documentation/networking/timestamping.txt > section 3: > "User space is responsible to ensure that multiple processes don't interfere > with each other and that the settings are reset." > > Add locking for the interface's HW timestamping mode to ensure that in a > setup with multiple ptp4l sessions sharing interfaces the sessions don't > overwrite each other's timestamping mode and that there is one session > responsible for resetting the mode on exit.
Is this intended to catch misconfigurations where different ptp4l instances are setting incompatible RX filters? If I understand the solution correctly, stopping ptp4l would break another ptp4l instance if they don't share the same filesystem (e.g. containers), or a different program is using HW timestamping (e.g. chronyd). -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
