summaryrefslogtreecommitdiffstats
path: root/tools/target_dec_fuzzer.c
diff options
context:
space:
mode:
authorNiklas Haas <[email protected]>2025-06-20 14:21:51 +0200
committerNiklas Haas <[email protected]>2025-06-22 12:13:09 +0200
commit27590d86534b0c94f12b9a206410f475fb008e72 (patch)
tree7f9d39e5453018c7840b1e55cd5d6f8909e40320 /tools/target_dec_fuzzer.c
parentbaad40bdd1e913e08c2851d4794bf880de153a3e (diff)
avutil/hwcontext_vulkan: disable host transfers if ReBAR is disabled
This feature fundamentally relies on host-visible VRAM, which restricts the set of available memory types to (typically) host-visible device-local ones. When resizable BAR is disabled, this memory type is usually limited to e.g. 256 MiB in size, which is just plain insufficient for allocation of general purpose GPU images, causing OOM errors on even the simplest of commands. The easiest solution is to disable host transfers entirely on machines without host-addressable VRAM. In theory, we could try and recover the use of host transfers for images which are *not* restricted to device-local memory types, but this is rarely the case in practice, and the effort required would exceed the benefit, especially since ReBAR is a standard feature on all platforms recent enough to have Vulkan drivers, and only occasionally disabled in the UEFI for by default for some hare-brained notion of "backwards compatibiility" with ancient software.
Diffstat (limited to 'tools/target_dec_fuzzer.c')
0 files changed, 0 insertions, 0 deletions