| /device/generic/vulkan-cereal/third-party/angle/src/libANGLE/ |
| D | ResourceMap_unittest.cpp | 23 std::vector<size_t> objects(kSize, 1); in TEST() local
26 resourceMap.assign(index + 1, &objects[index]); in TEST()
33 ASSERT_EQ(&objects[index], found); in TEST()
44 std::vector<size_t> objects(kSize, 1); in TEST() local
47 resourceMap.assign(index + 1, &objects[index]); in TEST()
60 std::vector<size_t> objects; in TEST() local
64 objects.push_back(index); in TEST()
69 objects.push_back(kLargeIndex); in TEST()
71 for (size_t &object : objects) in TEST()
76 for (size_t object : objects) in TEST()
[all …]
|
| /device/generic/vulkan-cereal/stream-servers/ |
| D | RenderThread.cpp | 196 void RenderThread::loadImpl(AutoLock* lock, const SnapshotObjects& objects) { in loadImpl() argument
197 snapshotOperation(lock, [this, &objects] { in loadImpl()
198 objects.readBuffer->onLoad(&*mStream); in loadImpl()
199 if (objects.channelStream) objects.channelStream->load(&*mStream); in loadImpl()
200 if (objects.ringStream) objects.ringStream->load(&*mStream); in loadImpl()
201 objects.checksumCalc->load(&*mStream); in loadImpl()
202 objects.threadInfo->onLoad(&*mStream); in loadImpl()
206 void RenderThread::saveImpl(AutoLock* lock, const SnapshotObjects& objects) { in saveImpl() argument
207 snapshotOperation(lock, [this, &objects] { in saveImpl()
208 objects.readBuffer->onSave(&*mStream); in saveImpl()
[all …]
|
| D | RenderThread.h | 83 bool doSnapshotOperation(const SnapshotObjects& objects,
86 void loadImpl(android::base::AutoLock* lock, const SnapshotObjects& objects);
87 void saveImpl(android::base::AutoLock* lock, const SnapshotObjects& objects);
|
| /device/generic/vulkan-cereal/protocols/vulkan/appendices/ |
| D | VK_KHR_external_memory.txt | 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_KHR_external_memory_fd.txt | 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_KHR_display.txt | 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_NV_external_memory.txt | 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_NV_external_memory_win32.txt | 24 Vulkan memory objects such that the underlying resources can be referenced
26 created in the Direct3D API to Vulkan memory objects.
32 1) If memory objects are shared between processes and APIs, is this
39 specific support usage within Vulkan for imported native memory objects, or
40 memory objects from other APIs.
|
| D | VK_KHR_external_memory_win32.txt | 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_NV_external_memory_capabilities.txt | 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_EXT_debug_marker.txt | 23 Vulkan objects, as well as additional commands for recording annotations of
35 objects in error messages.
136 and future proofing against future objects, it has notable downsides.
139 naming of implicitly created objects such as queues and swapchain images.
|
| D | VK_EXT_device_memory_report.txt | 22 objects.
118 5) Should we track bulk allocations shared among multiple objects?
122 Some implementations will let multiple slink:VkPipeline objects share the
128 Later, when the actual slink:VkPipeline objects are created by suballocating
130 handles of the slink:VkPipeline objects along with the actual suballocated
|
| D | VK_EXT_debug_utils.txt | 47 - The ability to identify specific Vulkan objects using a name or tag to
55 elink:VkDebugReportObjectTypeEXT to identify objects.
67 what objects are involved and potentially which location within a
89 Example uses: Create three callback objects.
155 objects in error messages.
312 and any new objects will need to be debugged using the new functionality
|
| D | VK_EXT_vertex_input_dynamic_state.txt | 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_capabilities.txt | 46 OS-native objects that have far more limited capabilities than the very
47 generic Vulkan memory objects.
48 Not all memory handle types can name memory objects that support 3D images,
|
| D | VK_KHR_8bit_storage.txt | 27 capabilities and allow access to 8-bit data in code:Block-decorated objects
28 in the code:Uniform and the code:StorageBuffer storage classes, and objects
|
| D | VK_ANDROID_external_memory_android_hardware_buffer.txt | 26 basetype:AHardwareBuffer objects created outside of the Vulkan device into
27 Vulkan memory objects, where they can: be bound to images and buffers.
43 1) Other external memory objects are represented as weakly-typed handles
52 objects generically.
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/ |
| D | fundamentals.txt | 11 different types of objects and shaders.
204 objects.
205 At the API level, all objects are referred to by handles.
218 device must: have a handle value that is unique among objects created on
231 All objects created or allocated from a sname:VkDevice (i.e. with a
251 low-frequency occurrences during runtime, allocating and freeing objects
253 Pool objects help accommodate improved performance of the allocations and
257 objects, and not to destroy them while they are still in use.
267 command and not further accessed by the objects they are used to create.
291 sname:VkDescriptorSetLayout objects may: be accessed by commands that
[all …]
|
| D | sparsemem.txt | 78 Support for creating sname:VkBuffer objects with the
81 Support for creating 2D single-sampled sname:VkImage objects with
84 Support for creating 3D sname:VkImage objects with
87 Support for creating 2D sname:VkImage objects with 2 samples and
90 Support for creating 2D sname:VkImage objects with 4 samples and
93 Support for creating 2D sname:VkImage objects with 8 samples and
96 Support for creating 2D sname:VkImage objects with 16 samples and
128 Both sname:VkBuffer and sname:VkImage objects created with the
138 resource must: be bound to one or more sname:VkDeviceMemory objects before
153 sname:VkBuffer objects created with the
[all …]
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_KHR_display_swapchain/ |
| D | create_shared_swapchains.txt | 20 swapchain objects when there is no more specific allocator available
23 handles in which the created swapchain objects will be returned.
27 and returns an array of swapchain objects.
|
| /device/generic/vulkan-cereal/third-party/googletest/docs/ |
| D | gmock_cheat_sheet.md | 100 2. Create the mock objects.
101 3. Optionally, set the default actions of the mock objects.
102 4. Set your expectations on the mock objects (How will they be called? What
104 5. Exercise code that uses the mock objects; if necessary, check the result
240 | `--gmock_catch_leaked_mocks=0` | Don't report leaked mock objects as failures. |
|
| /device/generic/vulkan-cereal/third-party/angle/extensions/ |
| D | EGL_EXT_device_query.txt | 46 for a method to access native GPU or device objects directly
50 native device objects from an EGL Display.
98 objects that exist only for the sake of enumeration and
103 Besides devices, objects are always specified by the combination
|
| D | EGL_ANGLE_iosurface_client_buffer.txt | 37 This extension allows creating EGL surfaces from IOSurface objects.
68 fashion are OpenVG VGImage objects and IOSurface objects."
|
| D | EGL_ANGLE_d3d_texture_client_buffer.txt | 41 objects.
69 | EGL_D3D_TEXTURE_ANGLE | Used for Direct3D11 texture objects |
100 fashion are OpenVG VGImage objects and Direct3D texture objects."
|
| /device/generic/vulkan-cereal/protocols/vulkan/chapters/VK_NVX_device_generated_commands/ |
| D | generation.txt | 40 Only registered objects at the time
84 Only registered objects at the time
118 The provided pname:objectTable must: include all objects referenced by
133 objects registered at reservation time.
|