<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jan 24, 2018 at 6:53 AM, Tapani Pälli <span dir="ltr"><<a href="mailto:tapani.palli@intel.com" target="_blank">tapani.palli@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This fixes test for me after Mesa commit 1f79d986af which will<br>
make device expose entrypoints only for enabled extensions.<br>
<br>
Signed-off-by: Tapani Pälli <<a href="mailto:tapani.palli@intel.com">tapani.palli@intel.com</a>><br>
---<br>
src/tests/func/sync/semaphore-<wbr>fd.c | 6 ++++++<br>
1 file changed, 6 insertions(+)<br>
<br>
diff --git a/src/tests/func/sync/<wbr>semaphore-fd.c b/src/tests/func/sync/<wbr>semaphore-fd.c<br>
index 69e56c2..a977a05 100644<br>
--- a/src/tests/func/sync/<wbr>semaphore-fd.c<br>
+++ b/src/tests/func/sync/<wbr>semaphore-fd.c<br>
@@ -45,9 +45,15 @@ struct buffer_layout {<br>
static void<br>
init_context(struct test_context *ctx, float priority)<br>
{<br>
+ const char *extension_names[] = {<br>
+ "VK_KHR_external_semaphore_fd"<wbr>,<br></blockquote><div><br></div><div>To be technically correct, we should enable all three external memory extensions and all three external fence extensions. With that,</div><div><br></div><div>Reviewed-by: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+ };<br>
+<br>
VkResult result = vkCreateDevice(t_physical_dev,<br>
&(VkDeviceCreateInfo) {<br>
.sType = VK_STRUCTURE_TYPE_DEVICE_<wbr>CREATE_INFO,<br>
+ .enabledExtensionCount = 1,<br>
+ .ppEnabledExtensionNames = extension_names,<br>
.queueCreateInfoCount = 1,<br>
.pQueueCreateInfos = &(VkDeviceQueueCreateInfo) {<br>
.sType = VK_STRUCTURE_TYPE_DEVICE_<wbr>QUEUE_CREATE_INFO,<br>
<span class="HOEnZb"><font color="#888888">--<br>
2.13.6<br>
<br>
</font></span></blockquote></div><br></div></div>