| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | queries.adoc | 5 [[queries]] anchor
13 <<queries-pools, Query Pool>>.
14 The state of these queries can: be read back on the host, or copied to a
17 The supported query types are <<queries-occlusion,Occlusion Queries>>,
18 <<queries-pipestats,Pipeline Statistics Queries>>,
20 <<queries-result-status-only, Result Status Queries>>,
23 <<queries-video-encode-feedback, Video Encode Feedback Queries>>
25 and <<queries-timestamps, Timestamp Queries>>.
27 <<queries-performance, Performance Queries>> are supported if the associated
31 <<queries-transform-feedback, Transform Feedback Queries>> are supported if
[all …]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/ |
| D | draw_mesh_common.adoc | 18 <<queries-transform-feedback, Transform Feedback Queries>> must: not be
23 <<queries-primitives-generated, Primitives Generated Queries>> must: not
28 <<queries-pipestats, Pipeline Statistics Query>> must: not contain
|
| D | query_begin_common.adoc | 8 All queries used by the command must: be _unavailable_
41 pname:query must: be less than the number of queries in pname:queryPool
66 or equal to the number of queries in pname:queryPool
73 a queue family index that supports <<queries-result-status-only,result
74 status queries>>, as indicated by
78 <<queries-operation-active,active>> queries
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_INTEL_performance_query/ |
| D | queries.adoc | 6 [[queries-performance-intel]]
9 Intel performance queries allow an application to capture performance data
11 Performance queries are used in a similar way than other types of queries.
12 A main difference with existing queries is that the resulting data should be
16 [open,refpage='vkInitializePerformanceApiINTEL',desc='Initialize a device for performance queries',…
19 performance queries with the call:
23 * pname:device is the logical device used for the queries.
45 …ninitializePerformanceApiINTEL',desc='Uninitialize a device for performance queries',type='protos']
48 for performance queries with the call:
52 * pname:device is the logical device used for the queries.
[all …]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_GOOGLE_surfaceless_query.adoc | 11 where EGL is able to respond to certain queries before a surface is created,
12 while Vulkan requires a surface for corresponding queries.
36 surface, and such queries could in fact be answered before a surface is
46 One solution is to modify the existing relevant queries to allow querying
|
| D | VK_EXT_calibrated_timestamps.adoc | 21 …er exceeds the size of the value that can be returned, which with 64-bit queries is, for most purp…
32 To avoid this extra complication, this extension requires that timer queries are monotonic; a futur…
37 * Provide queries describing how to convert between different timer values
132 …r reporting the maximum deviation of the timestamp values returned by calibrated timestamp queries?
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_KHR_ray_query.adoc | 67 visibility and ray tracing for secondary queries.
69 Ray queries are available to all shader types, including graphics, compute
71 Ray queries are not able to launch additional shaders, instead returning
90 Example of ray query in a GLSL shader, illustrating how to use ray queries
121 ** `apiext:VK_KHR_ray_query` (for ray queries in existing shader stages)
|
| D | VK_KHR_performance_query.adoc | 36 We extend elink:VkQueryType to add a new query type for performance queries,
38 performance queries to enable.
47 *RESOLVED* No - queries are tied to command buffer creation and thus have to
50 2) Should this extension include a mechanism to begin and end queries
84 8) Should we allow performance queries to interact with multiview?
86 *RESOLVED* Yes, but the performance queries must be performed once for each
89 9) Should a `queryCount > 1` be usable for performance queries?
218 // that will use performance queries
|
| D | VK_KHR_get_display_properties2.adoc | 19 This extension provides new queries for device display properties and
21 introducing any further queries.
|
| D | VK_KHR_get_surface_capabilities2.adoc | 20 This extension provides new queries for device surface capabilities that can
22 queries.
|
| D | VK_KHR_get_physical_device_properties2.adoc | 21 This extension provides new queries for device features, device properties,
23 without introducing any further queries.
|
| D | VK_KHR_video_encode_queue.adoc | 87 ** Replace `VK_QUERY_TYPE_VIDEO_ENCODE_BITSTREAM_BUFFER_RANGE_KHR` queries
88 with more generic `VK_QUERY_TYPE_VIDEO_ENCODE_FEEDBACK_KHR` queries
110 flag to video encode feedback queries
|
| D | VK_EXT_host_query_reset.adoc | 23 This extension adds a new function to reset queries from the host.
|
| D | VK_EXT_pipeline_properties.adoc | 61 all queries using this entry point?
74 as the basis for other pipeline property queries without requiring the
|
| D | VK_KHR_external_semaphore_capabilities.adoc | 25 This extension provides a set of capability queries and handle definitions
|
| D | VK_GOOGLE_surfaceless_query.adoc | 30 *This can only be supported on platforms where the results of these queries
|
| D | VK_KHR_external_fence_capabilities.adoc | 27 This extension provides a set of capability queries and handle definitions
|
| D | VK_KHR_get_memory_requirements2.adoc | 22 This extension provides new queries for memory requirements of images and
|
| D | VK_KHR_surface.adoc | 81 enabled extensions and features) for the queries, Vulkan was released only
85 or parameters, via extensible versions of the queries:
200 queries in this extension.
|
| /hardware/google/gfxstream/guest/renderControl_enc/ |
| D | README | 10 This function queries the host renderer version number.
13 This function queries the host renderer for the EGL version
17 This function queries the host for EGL string (.i.e EGL_EXTENSIONS).
24 queries the host for the number of supported EGL configs.
29 This function queries the host for the all set of supported configs
52 queries the host for framebuffer parameter, see renderControl_types.h
128 This function queries the host for the pixel content of a colorBuffer's
|
| /hardware/google/gfxstream/codegen/magma/ |
| D | README.md | 16 …ut` to map and populate the result buffer contents. Note that as certain queries may return a vari…
52 …is used to illustrate handling of variable-size queries, as may be encountered in vendor-specific …
|
| /hardware/interfaces/media/c2/1.0/ |
| D | IConfigurable.hal | 52 * queries that require blocking must be skipped.
195 * The object must process all fields queried even if some queries fail.
214 * @param inFields List of field queries.
228 * supplied queries.
|
| /hardware/google/gfxstream/include/OpenGLESDispatch/ |
| D | gles3_only_functions.h | 93 X(void, glGenQueries, (GLsizei n, GLuint * queries), (n, queries)) \
94 X(void, glDeleteQueries, (GLsizei n, const GLuint * queries), (n, queries)) \
|
| /hardware/google/gfxstream/host/gl/OpenGLESDispatch/ |
| D | gles3_only_dispatch_logging_wrappers.impl | 419 void glGenQueries_dispatchLoggingWrapper(GLsizei n, GLuint * queries) {
420 DISPATCH_DEBUG_LOG("glGenQueries(n:%d, queries:%p)", n, queries);
421 GLDispatch::glGenQueries_underlying(n, queries);
424 void glDeleteQueries_dispatchLoggingWrapper(GLsizei n, const GLuint * queries) {
425 DISPATCH_DEBUG_LOG("glDeleteQueries(n:%d, queries:%p)", n, queries);
426 GLDispatch::glDeleteQueries_underlying(n, queries);
|
| D | gles3_only.entries | 64 # More vertex attribute setters / queries
124 void glGenQueries(GLsizei n, GLuint * queries);
125 void glDeleteQueries(GLsizei n, const GLuint * queries);
|