1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
// Copyright 2017-2023 The Khronos Group Inc.
//
// SPDX-License-Identifier: CC-BY-4.0
include::{generated}/meta/{refprefix}VK_KHR_pipeline_executable_properties.adoc[]
=== Other Extension Metadata
*Last Modified Date*::
2019-05-28
*IP Status*::
No known IP claims.
*Interactions and External Dependencies*::
*Contributors*::
- Faith Ekstrand, Intel
- Ian Romanick, Intel
- Kenneth Graunke, Intel
- Baldur Karlsson, Valve
- Jesse Hall, Google
- Jeff Bolz, Nvidia
- Piers Daniel, Nvidia
- Tobias Hector, AMD
- Jan-Harald Fredriksen, ARM
- Tom Olson, ARM
- Daniel Koch, Nvidia
- Spencer Fricke, Samsung
=== Description
When a pipeline is created, its state and shaders are compiled into zero or
more device-specific executables, which are used when executing commands
against that pipeline.
This extension adds a mechanism to query properties and statistics about the
different executables produced by the pipeline compilation process.
This is intended to be used by debugging and performance tools to allow them
to provide more detailed information to the user.
Certain compile time shader statistics provided through this extension may
be useful to developers for debugging or performance analysis.
include::{generated}/interfaces/VK_KHR_pipeline_executable_properties.adoc[]
=== Issues
1) What should we call the pieces of the pipeline which are produced by the
compilation process and about which you can query properties and statistics?
*RESOLVED*: Call them "`executables`".
The name "`binary`" was used in early drafts of the extension but it was
determined that "`pipeline binary`" could have a fairly broad meaning (such
as a binary serialized form of an entire pipeline) and was too big of a
namespace for the very specific needs of this extension.
=== Version History
* Revision 1, 2019-05-28 (Faith Ekstrand)
** Initial draft
|
