d19af88f happens to change test_transfer_notify_EventNotify() and
that affects test_GetDuration().

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55422

Needed by Lenovo Ready For Assistant.

They're not going to match anyway.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>

Check for Rosetta before extracting the port right, since we won't need
it in that case anyway.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=20694

lParam being NULL is handled in win32u/defwnd.c so make sure to pass the NULL
through rather than relying on the pointer always being valid since it may not
be in this case.

The result of abs(INT_MIN) is INT_MIN, which breaks the ulps comparison.

For discard maps on deferred contexts, we currently blit from the upload buffer
to the resource. This is necessary because command lists can be reused and
submitted multiple times—we cannot simply have the buffer take ownership, as for
discard maps on immediate contexts.

However, it is very common for applications to use command lists only once
before throwing them away—in essence taking advantage of the feature only for
the multithreading advantages it allows.

Therefore we take advantage of this pattern by trying to rename the buffer
anyway. In order to do this we introduce a refcount for BO pointers. When
writing to a buffer BO, we first check whether the buffer "owns" the BO—i.e.
whether it has a refcount of 1—and if not, we create a new BO for the buffer and
copy the contents of the old BO to the new BO. That is, we perform
mostly-transparent copy-on-write.

This improves performance, and reduces CPU usage, in Assassin's Creed: Unity.

Mostly just because wined3d_context_vk_apply_draw_state() is large and it's nice
to split it up a bit.

This makes it easier to invalidate in the case where multiple resources share
the same BO, which in turn is necessary to implement copy-on-write semantics for
BOs.

This is also necessary if we ever want to evict resources which have views,
although it's not clear if this will ever be necessary. If nothing else, though,
it removes that implicit dependency.