nouveau: map_range returning -EBUSY isn't necessarily an error

diff --git a/src/gallium/drivers/nouveau/nouveau_screen.c b/src/gallium/drivers/nouveau/nouveau_screen.c
index 832366e646257728657131c184322563cff0dc09..e4cf91c005c4d5d9a9ba8ac8d936e097e7e65d10 100644 (file)
--- a/src/gallium/drivers/nouveau/nouveau_screen.c
+++ b/src/gallium/drivers/nouveau/nouveau_screen.c
@@ -4,6 +4,8 @@
 
 #include <util/u_memory.h>
 
+#include <errno.h>
+
 #include "nouveau/nouveau_bo.h"
 #include "nouveau_winsys.h"
 #include "nouveau_screen.h"
@@ -141,12 +143,13 @@ nouveau_screen_bo_map_range(struct pipe_screen *pscreen, struct pipe_buffer *pb,
                            unsigned offset, unsigned length, unsigned usage)
 {
        struct nouveau_bo *bo = nouveau_bo(pb);
+       uint32_t flags = nouveau_screen_map_flags(usage);
        int ret;
 
-       ret = nouveau_bo_map_range(bo, offset, length,
-                                  nouveau_screen_map_flags(usage));
+       ret = nouveau_bo_map_range(bo, offset, length, flags);
        if (ret) {
-               debug_printf("map_range failed: %d\n", ret);
+               if (!(flags & NOUVEAU_BO_NOWAIT) || ret != -EBUSY)
+                       debug_printf("map_range failed: %d\n", ret);
                return NULL;
        }