On Wed, Feb 15, 2023 at 10:27:15PM -0800, Matt Corallo wrote: > My naive solution from skimming the code would be to shove > formerly-discarded samples into a global limited queue and check for > available timestamps in `phc_poll`. However, I have no idea if the time > difference between when the sample was taken by the hardware and when the > `HCL_CookTime` call is done would impact accuracy (or maybe the opposite, > since we'd then be cooking time with the hardware clock right after taking > the HCL sample rather than when the PHC timestamp happens), or if such a > patch would simply be rejected as a dirty, dirty hack rather than unifying > the PHC read sockets across the devices into one socket (via some global > tracking the device -> socket mapping?) and passing the samples out > appropriately. Let me know what makes the most sense here.
My first thought is that this should be addressed in the kernel, so even different processes having open the PHC device can receive all extts samples. If it turns out it's too difficult to do for the character device (I'm not very familiar with that subsystem), maybe it could be done at least in sysfs (/sys/class/ptp/ptp*/fifo or a new file showing the last event like the PPS assert and clear). -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
