|| So how do you know the program is un-erring? | | It detects mutliple _physical_ processors (that's the case where | the lock prefix is certainly necessary). I wonder if the 'lock' | is necessary for multiple _logical_ processors.But how would you know that the test's result is 100% reliable? I mean, running the test for a year instead of an hour might not yield the same result, because it could take a long time to get the processor into the right state for the opposite result. Also a slight variation of your particular test might hit the opposite result right away, while your incarnation never does. Can you afford to rely on your test result, and have your actual production code fail in the field, once deployed? |