| /hardware/google/gfxstream/guest/mesa/bin/ |
| D | refcnt-log-helper.py | 45 objects = {}
58 if cur_object in objects:
59 del objects[cur_object]
63 objects[cur_object] = []
64 if prev_object in objects:
65 objects[prev_object] += stack
72 for stack in objects.values():
|
| /hardware/google/gfxstream/host/ |
| D | RenderThread.cpp | 210 void RenderThread::loadImpl(AutoLock* lock, const SnapshotObjects& objects) { in loadImpl() argument
211 snapshotOperation(lock, [this, &objects] { in loadImpl()
212 objects.readBuffer->onLoad(&*mStream); in loadImpl()
213 if (objects.channelStream) objects.channelStream->load(&*mStream); in loadImpl()
214 if (objects.ringStream) objects.ringStream->load(&*mStream); in loadImpl()
215 objects.checksumCalc->load(&*mStream); in loadImpl()
216 objects.threadInfo->onLoad(&*mStream); in loadImpl()
220 void RenderThread::saveImpl(AutoLock* lock, const SnapshotObjects& objects) { in saveImpl() argument
221 snapshotOperation(lock, [this, &objects] { in saveImpl()
222 objects.readBuffer->onSave(&*mStream); in saveImpl()
[all …]
|
| D | RenderThread.h | 87 bool doSnapshotOperation(const SnapshotObjects& objects,
90 void loadImpl(android::base::AutoLock* lock, const SnapshotObjects& objects);
91 void saveImpl(android::base::AutoLock* lock, const SnapshotObjects& objects);
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_metal_objects.adoc | 12 platforms, provides the ability to import and export the underlying Metal objects
13 associated with specific Vulkan objects.
19 many Vulkan objects have a corresponding Metal equivalent that provides the underlying
21 for the app to be able to interact directly with these Metal objects:
35 to managing access to Metal objects, this extension proposes to provide a single unified
36 interface to all Metal objects providing functionality to the layered Vulkan implementation.
38 new Metal objects that might be introduced in the future.
48 To export underlying Metal objects from Vulkan objects, this extension adds one new
63 additional Metal objects, through the future addition of new export object structures.
118 To export Metal objects from Vulkan objects, the app must first indicate the
[all …]
|
| /hardware/google/gfxstream/guest/mesa/src/vulkan/runtime/ |
| D | vk_log.c | 87 struct vk_object_base **objects = NULL; in __vk_log_impl() local
91 objects = (struct vk_object_base **) objects_or_instance; in __vk_log_impl()
93 if (unlikely(objects[i] == NULL)) { in __vk_log_impl()
98 if (unlikely(!objects[i]->client_visible)) { in __vk_log_impl()
100 "of type %s", objects[i], in __vk_log_impl()
101 vk_ObjectType_to_str(objects[i]->type)); in __vk_log_impl()
105 instance = vk_object_to_instance(objects[i]); in __vk_log_impl()
108 assert(vk_object_to_instance(objects[i]) == instance); in __vk_log_impl()
182 struct vk_object_base *base = objects[i]; in __vk_log_impl()
262 vk_debug_report(instance, flags, object_count ? objects[0] : NULL, 0, in __vk_log_impl()
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_EXT_metal_objects.adoc | 21 underlying Metal objects associated with specific Vulkan objects.
26 flink:vkExportMetalObjectsEXT, to export underlying Metal objects from
27 Vulkan objects, and supports importing the appropriate existing Metal
28 objects when creating Vulkan objects of types slink:VkDeviceMemory,
|
| D | VK_KHR_external_memory_fd.adoc | 23 handles from Vulkan memory objects and to import Vulkan memory objects from
24 POSIX file descriptor handles exported from other Vulkan memory objects or
45 This would indicate there are actually multiple memory objects, rather than
|
| D | VK_EXT_device_address_binding_report.adoc | 25 objects.
50 *RESOLVED*: The extension covers all Vulkan objects, and is not restricted
51 to objects backed by VkDeviceMemory objects.
57 4.) Can multiple Vulkan objects share an overlapping virtual address range?
78 address ranges for which there are no related API objects visible to the
110 Do we need queries or properties indicating which Vulkan objects will report
115 virtual ranges to objects.
|
| D | VK_NV_external_memory.adoc | 24 objects such that the underlying resources can be referenced outside the
31 1) If memory objects are shared between processes and APIs, is this
38 specific support usage within Vulkan for imported native memory objects, or
39 memory objects from other APIs.
|
| D | VK_EXT_vertex_input_dynamic_state.adoc | 21 pipeline state objects that need to be created, is the vertex input binding
24 pipeline objects they need to create.
|
| D | VK_KHR_external_memory.adoc | 36 Vulkan memory objects such that the underlying resources can be referenced
69 2) If memory objects are shared between processes and APIs, is this
160 with the objects represented by the external handles, and rely on the
162 objects with a single image or buffer.
180 objects.
186 If new objects backed by memory objects are added to the API, they too can
214 relying on native handles to define the external objects?
225 included in memory objects for those memory objects that may be exported?
227 *RESOLVED*: Implementations must ensure that sharing memory objects does not
230 objects explicitly shared.
[all …]
|
| D | VK_QNX_external_memory_screen_buffer.adoc | 20 code:_screen_buffer objects created outside of the Vulkan device into Vulkan
21 memory objects, where they can be bound to images and buffers.
|
| D | VK_NV_external_memory_capabilities.adoc | 35 *RESOLVED*: This is because some handle types are based on OS-native objects
37 objects.
38 Not all memory handle types can name memory objects that support 3D images,
|
| D | VK_KHR_external_memory_win32.adoc | 24 memory objects and to import Vulkan memory objects from Windows handles
25 exported from other Vulkan memory objects or from similar resources in other
|
| D | VK_KHR_display.adoc | 46 into separate objects.
52 immutable objects.
129 11) Should displays and/or modes be dispatchable objects? If functions are
131 dispatchable objects as defined in Khronos bug 13529.
132 If they are not added to the list of dispatchable objects, functions
135 There is no performance case against making them dispatchable objects, but
136 they would be the first extension objects to be dispatchable.
189 18) What should the lifetime of display and built-in display mode objects
193 These objects cannot be destroyed.
194 A future extension may be added to expose a way to destroy these objects
[all …]
|
| D | VK_EXT_shader_object.adoc | 49 Shader objects provide a more flexible alternative to slink:VkPipeline
50 objects, which may be helpful in certain use cases.
129 // Vertex and fragment shader objects created above
166 // Graphics shader objects may only be used to draw inside dynamic render pass
302 // Vertex, geometry, and fragment shader objects created above
329 // Graphics shader objects may only be used to draw inside dynamic render pass
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_object_refresh/ |
| D | copies.adoc | 24 implementation to refresh the internal data of specific objects from a
27 [open,refpage='vkCmdRefreshObjectsKHR',desc='Execute a pipelined refresh of a list of objects',type…
29 To refresh a list of objects as a pipelined operation, call:
36 structure specifying the list of objects to refresh.
53 [open,refpage='VkRefreshObjectListKHR',desc='Structure specifying a list of objects to refresh',typ…
62 * pname:objectCount is the number of objects to refresh.
64 structures, defining the objects to refresh.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/ |
| D | memory_reservation_request_count_combined_common.adoc | 6 // Common to creating objects
10 pname:device across all slink:{combinedparentobject} objects plus
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_NV_clip_space_w_scaling/ |
| D | vertexpostproc.adoc | 59 ifdef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>, or]
60 ifndef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>.]
106 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_display_swapchain/ |
| D | create_shared_swapchains.adoc | 25 swapchain objects when there is no more specific allocator available
28 handles in which the created swapchain objects will be returned.
32 and returns an array of swapchain objects.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_metal_objects/ |
| D | device_memory.adoc | 5 [[metal-objects]]
10 supports the ability to import and export the underlying Metal objects
11 associated with specific Vulkan objects.
13 The underlying Metal objects associated with certain Vulkan objects can be
14 exported from those Vulkan objects using the pname:pNext chain of the
24 object, or one or more existing Metal code:MTLTexture objects, by including
25 those Metal objects in either slink:VkImportMetalIOSurfaceInfoEXT or
29 …eInfoEXT',desc='Structure that identifies the Metal objects that can be exported from Vulkan objec…
31 To export Metal objects from Vulkan objects, the app must: first indicate
56 Bits which indicate the types of Metal objects that may be exported from a
[all …]
|
| /hardware/google/gfxstream/ |
| D | README.md | 104 and [objects](https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/docs/vulkan/base-objs.rst).
105 - Currently, there are a set of Mesa objects and gfxstream objects. For example,
110 objects will be phased out and Mesa objects used exclusively.
|
| /hardware/interfaces/neuralnetworks/utils/ |
| D | README.md | 56 Some notes about HIDL interface objects and lifetimes across processes:
58 All HIDL interface objects inherit from `IBase`, which itself inherits from `::android::RefBase`. As
59 such, all HIDL interface objects are reference counted and must be owned through `::android::sp` (or
60 referenced through `::android::wp`). Allocating `RefBase` objects on the stack will log errors and
65 HIDL/Binder manages the reference count of HIDL interface objects automatically across processes. If
104 to quickly return, and the results are returned at a later time through these callback objects.
125 object that is a direct analog of HIDL `DeathHandler`, only using libbinder_ndk objects for
|
| /hardware/interfaces/wifi/supplicant/1.1/ |
| D | ISupplicantStaIface.hal | 33 * Registration of multiple callback objects is supported. These objects must
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | fragops.adoc | 318 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
369 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
403 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
474 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
604 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
667 ifdef::VK_EXT_shader_object[when drawing using <<shaders-objects, shader objects>>, or]
715 ifdef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>, or]
716 ifndef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>.]
1108 ifdef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>, or]
1109 ifndef::VK_EXT_extended_dynamic_state3[when drawing using <<shaders-objects, shader objects>>.]
[all …]
|