trace CcdCallFnAfter() causality
NAMD uses CcdCallFnAfter() to poll for GPU completion, which breaks the causality chain. It should be possible to trace a chain of CcdCallFnAfter() calls back to the entry method that called the first one.
#6 Updated by Ronak Buch 4 months ago
- Status changed from New to In Progress
I think this is doable, but the detail of functions coming from a CcdCallFnAfter may be a bit suspect (since it just calls a function directly, so it's hard for the RTS to know what's executing) and the ordering causality chain may include extraneous calls due to differing levels of delays for different invocations of CcdCallFnAfter. Regardless, getting causation to the right place may be a bit tricky without adding significantly more disambiguation code to adding stuff to the CcdCallFnAfter call. I've started toying with an implementation to see if I can get it to work correctly or not.