Re: [PATCH 0/3] MR87: vkd3d: Hold locks to read protected variables

[Conor McCarthy (＠cmccarthy)]

I don't think we need to lock the fence mutex before checking max_pending_value. All cases which update max_pending_value lead to a new call to d3d12_command_queue_flush_ops(), except for updates from vkd3d_wait_for_gpu_timeline_semaphore(), which are not relevant because higher values being waited on there have already been included in max_pending_value.