-
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
5 changed files
with
162 additions
and
5 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,34 @@ | ||
// 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. | ||
*Contributors*:: | ||
- Jason Ekstrand, Collabora | ||
|
||
=== Description | ||
|
||
This extension allows a client to request that flink:vkMapMemory 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? | ||
|
||
*PROPOSED*: The memory object should be left unmapped and flink:vkMapMemory | ||
should return ename:VK_ERROR_MEMORY_MAP_FAILED. | ||
|
||
=== 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
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