clover/api: make use of validate_mem_migration_flags in clEnqueueMigrateMemObjects

Signed-off-by: Karol Herbst <kherbst@redhat.com>
Reviewed-by: Francisco Jerez <currojerez@riseup.net>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6401>

diff --git a/src/gallium/frontends/clover/api/transfer.cpp b/src/gallium/frontends/clover/api/transfer.cpp
index 7468bd6..b5ed663 100644 (file)
--- a/src/gallium/frontends/clover/api/transfer.cpp
+++ b/src/gallium/frontends/clover/api/transfer.cpp
@@ -911,16 +911,13 @@ clEnqueueMigrateMemObjects(cl_command_queue d_q,
    auto deps = objs<wait_list_tag>(d_deps, num_deps);
 
    validate_common(q, deps);
+   validate_mem_migration_flags(flags);
 
    if (any_of([&](const memory_obj &m) {
          return m.context() != q.context();
          }, mems))
       throw error(CL_INVALID_CONTEXT);
 
-   if (flags & ~(CL_MIGRATE_MEM_OBJECT_HOST |
-                 CL_MIGRATE_MEM_OBJECT_CONTENT_UNDEFINED))
-      throw error(CL_INVALID_VALUE);
-
    auto hev = create<hard_event>(
       q, CL_COMMAND_MIGRATE_MEM_OBJECTS, deps,
       [=, &q](event &) {