Hi, I wasn't quite sure how osdMonotonicResolution got used and I didn't know if I could guarantee that 1e9 / freq would always be an integer multiple, so I though it safest to round up so as not to promise a resolution that was not possible. However if returning 101ns rather than 100ns causes issues then the logic could be changed to check for an exact integer multiple and not add 1 in those cases.
@Micahel I have found PerfCounter quite good on a VM - that was originally how I started using it years ago as the normal clock on our VMs was pretty bad and kept losing time and then being corrected and jumping, but the performance counter seemed to come directly from the real hardware hosting the VM and so was very stable.
--
https://code.launchpad.net/~freddie-akeroyd/epics-base/+git/epics-base/+merge/391018
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.
- References:
- [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Next:
epics-pva2pva-linux32 - Build # 195 - Unstable! APS Jenkins via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 Freddie Akeroyd via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:fix_win32_monotonic_time into epics-base:7.0 mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|