vgsp-sema: keep displaced injected pins and fan pool releases out to them (ISSUE-0002)

Two host tools can inject conflicting PAs for the same pool-semaphore VA
page; the pin table is one entry per page, so the later store won and the
release written through the loser was invisible while the client polled
the winner forever (observed r22/r24: fresh va=0x121000000 -> pa matched
the client pagemap; a later stale pair overwrote it, the single release
write landed on the stale page, and the second client spun in UVM
registration). Remember the displaced pair and write the release to it as
well: forward-only and read-back proven, best effort, sequential clients
only (documented in the helper).

0 files changed, 0 insertions, 0 deletions