zink: initialize dispatch-table before queue-init
This matters in the next patch, where we call vk-functions through the dispatch-table instead. Reviewed-by: Hoe Hao Cheng <haochengho12907@gmail.com> Reviewed-By: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11550>
This commit is contained in:
committed by
Marge Bot
parent
9e9ead2c15
commit
1b6ed06527
@@ -2099,6 +2099,8 @@ zink_internal_create_screen(const struct pipe_screen_config *config)
|
||||
if (!screen->dev)
|
||||
goto fail;
|
||||
|
||||
vk_device_dispatch_table_load(&screen->vk.device, &vkGetDeviceProcAddr, screen->dev);
|
||||
|
||||
init_queue(screen);
|
||||
if (screen->info.driver_props.driverID == VK_DRIVER_ID_MESA_RADV ||
|
||||
screen->info.driver_props.driverID == VK_DRIVER_ID_AMD_OPEN_SOURCE ||
|
||||
@@ -2106,8 +2108,6 @@ zink_internal_create_screen(const struct pipe_screen_config *config)
|
||||
/* this has bad perf on AMD */
|
||||
screen->info.have_KHR_push_descriptor = false;
|
||||
|
||||
vk_device_dispatch_table_load(&screen->vk.device, &vkGetDeviceProcAddr, screen->dev);
|
||||
|
||||
zink_verify_device_extensions(screen);
|
||||
|
||||
if (screen->info.have_EXT_calibrated_timestamps && !check_have_device_time(screen))
|
||||
|
||||
Reference in New Issue
Block a user