Searched refs:collisions (Results 1 – 15 of 15) sorted by relevance
1 # we reject collisions between commands and types
39 unsigned long collisions; member
17 # avoid collisions with perf (perf) and mesa-demos (offset)
19 # An optional prefix for the download file in the case of name collisions
29 # to prevent collisions.
8 its internal defines with '__db_', to avoid collisions.
1096 st->collisions = tswap32(st->collisions); in host_to_target_data_link_rtattr()1129 st64->collisions = tswap64(st64->collisions); in host_to_target_data_link_rtattr()
152 of spatially close collisions is very low. Distant collisions are not a
101 collisions.
100 QEMU will not try to resolve collisions and will report an error if the
115 # Instead, prefix the overlay override value with 'rwfs-' to avoid collisions.
228 downloaded file is useful for avoiding collisions in
317 also automatically identifies any collisions or "conflicts" that
1221 will be no collisions between type, command, and event names.
1989 the same 9p export in order to avoid file ID collisions on guest.1996 collisions on guest. Remapping inodes in such cases is required2008 in this case that would prevent file ID collisions on guest. This