I noticed you clarified what '!interrupted' means in idle, thanks. And now the sync interrupt name makes sense too.
Of course some more questions spring immediately to mind after a quick browse (sorry!) and might be worth considering for it's release if not already in the pipeline:
How are sync/wand/mbkpt is propagated, e.g. via write mesh or separate oob signal? Is it only on-chip? Which mesh does multicast use/can it work over external links? Are there alignment restrictions/deadlock caveats with gie+wand+idle as per the gie+idle thread? How is the membership of the group specified for wand? (as in 'When all cores in a group have set their respective wand bits').Statistics: Posted by notzed — Tue Oct 01, 2013 2:29 am
]]>