-
Notifications
You must be signed in to change notification settings - Fork 476
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a new extension: VK_EXT_map_memory_placed
- Loading branch information
Showing
6 changed files
with
454 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
// Copyright 2017-2022 The Khronos Group Inc. | ||
// | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
include::{generated}/meta/{refprefix}VK_EXT_map_memory_placed.txt[] | ||
|
||
=== Other Extension Metadata | ||
|
||
*Last Modified Date*:: | ||
2022-07-28 | ||
*IP Status*:: | ||
No known IP claims. | ||
*Interactions and External Dependencies*:: | ||
- Interacts with apitext:VK_EXT_external_memory_host | ||
*Contributors*:: | ||
- Jason Ekstrand, Collabora | ||
- Tobias Hector, AMD | ||
- Georg Lehmann, Valve | ||
- Derek Lesho, Codeweavers | ||
|
||
=== Description | ||
|
||
This extension allows a client to request that flink:vkMapMemory2EXT | ||
attempt to place the memory map at a particular virtual address. | ||
|
||
include::{generated}/interfaces/VK_EXT_map_memory_placed.txt[] | ||
|
||
=== Issues | ||
|
||
1) What should happen if the implementation cannot place the memory map at | ||
the requested address? | ||
|
||
*RESOLVED*: The memory object should be left unmapped and | ||
flink:vkMapMemory2EXT should return ename:VK_ERROR_MEMORY_MAP_FAILED. | ||
|
||
2) How can a client atomically re-reserve the address range on unmap? | ||
|
||
*RESOLVED*: When `VK_MEMORY_UNMAP_RESERVE_BIT_EXT` is passed to | ||
`vkUnmapMemory2EXT()`, the implementation unmaps the memory range in such a | ||
way that the range is automatically re-reserved. With `mmap()`, this is | ||
accomplished by simply mapping over the range with another anonymous | ||
mapping. However, allowing this with `vkMapMemory()` would break Vulkan's | ||
concept of when a memory object is or is not mapped. | ||
|
||
=== Version History | ||
|
||
* Revision 0, 2022-07-27 (Jason Ekstrand) | ||
** Internal revisions |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.