[ts-general] is this a violation?
R P Herrold
herrold at owlriver.com
Wed May 22 09:45:10 EDT 2013
On Wed, 22 May 2013, David wrote:
> Well, it turns out that in testing, I had not locked the shim to a
> single cpu, causing the timing issue on my system. Not a shim bug.
> Sorry, and thanks!
* nod * Glad the Heisenbug went away
I do not quite understand about locking a process to a single
processor --- the shim handles multi-core and multiple
processors without special attention in the general case we
have seen. Are you in a hypervisor or virtualization
environment (VMWare, or such)?
-- Russ herrold
More information about the ts-general