While working on the unified block allocator, radv doesn't seem to properly invalidate a mapped memory range that is a sub mapping of the whole memory block. issue stops if the mapped region exactly matches the block size (not sure if this is the reason)
While working on the unified block allocator, radv doesn't seem to properly invalidate a mapped memory range that is a sub mapping of the whole memory block. issue stops if the mapped region exactly matches the block size (not sure if this is the reason)
check commit 2565f08 vs 2584c74