The SafepointMechanism class has been used to perform safepoint operations. Now we also perform handshake operations, and soon also concurrent stack processing. Therefore, names such as SafepointMechanism::should_block no longer sound right, when the real questino is whether it should process an operation (be that a safepoint, handshake or whatever else).