Bug 109807

Summary: Add more granular multiarch usage for Mesa Vulkan overlay JSON manifest
Product: Mesa Reporter: Shmerl <shtetldik>
Component: Drivers/Vulkan/CommonAssignee: mesa-dev
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: airlied, chadversary, daniel
Version: git   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Shmerl 2019-03-01 18:15:33 UTC 
After recent changes, VkLayer_MESA_overlay.json references implicit libVkLayer_MESA_overlay.so which supposedly should be accessible to the loader (either in common library cache or through LD_LIBRARY_PATH).

It would be better for it to use explicit reference, similar to how actual Vulkan ICD manifests are doing it. But for that, there should be separate JSON loader manifest for each architecture. Is it currently possible?

Actual ICDs do support it, i.e. you can find:

/usr/share/vulkan/icd.d/radeon_icd.i686.json
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json

So loader knows which one to pick depending on the arch even during implicit loading.

Would it work for layers?

I.e. for example:

/usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.i686.json
/usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.x86_64.json

Each of them referencing explicit .so location? Or that requires fixing the layer loading logic first?

I also opened this to be able to load layer JSON explicitly, like ICD manifests allow:

https://github.com/KhronosGroup/Vulkan-Loader/issues/154
Comment 1 Lionel Landwerlin 2019-03-02 23:16:56 UTC 
Sounds like a good idea, I should have looked at the icd for the previous fix.
Comment 3 GitLab Migration User 2019-09-18 18:13:17 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/182.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.