| commit | 81597759beff0729057887340e219e87448d1a4c | [log] [tgz] |
|---|---|---|
| author | Duncan Hopkins <duncan@thefoundry.co.uk> | Wed Aug 14 11:11:19 2019 +0100 |
| committer | Marge Bot <eric+marge@anholt.net> | Fri Nov 06 17:15:05 2020 +0000 |
| tree | 1c73181958d2739a032a4bc39a9b60102f08749d | |
| parent | f0bbd8fdd0871ca9afdda107764818026bce13fe [diff] |
zink: For MoltenVk added vkFlushMappedMemoryRanges() to vkMapMemory() to fix empty mapped memory. On MoltenVK/MacOS when mapping memory that should already have content it does not appear until flushed. This noticably effects vertex attribute uploads to descrete devices. Did also try to add the Coherent memory flag, which did work, until there the Coherent type could only be used for transfer usage only. This is a known limitation of MoltenVK. See https://github.com/KhronosGroup/MoltenVK/blob/master/Docs/MoltenVK_Runtime_UserGuide.md#known-moltenvk-limitations Seen when using MoltenVK 1.0.121, 1.2.131 Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-By: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7470>