Consider to add a new error code for `urVirtualMemMap` when the VA is already mapped about unified-runtime

[kbenzie]

This could be UR_RESULT_ERROR_INVALID_OPERATION instead. However looking at urVirtulMemMap spec, UR_RESULT_ERROR_INVALID_VALUE isn't listed as a valid return value. Will need to update the spec either way.

[pbalcer]

For the sanitizer we'd ideally have a dedicated error code for VA already having a physical mapping, because in that case it essentially means "success". Using a generic error code like invalid operation might lead to it being reused later on for something different.

[AllanZyne]

For the sanitizer we'd ideally have a dedicated error code for VA already having a physical mapping, because in that case it essentially means "success". Using a generic error code like invalid operation might lead to it being reused later on for something different.

Yes, I totally agree. But if we can document that "UR_RESULT_ERROR_INVALID_OPERATION" only means the VA is already mapped but not other reasons, I think using the existing error code is fine as well.