BO (reference) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:BO (Results 1 – 12 of 12) sorted by relevance

/linux/Documentation/accel/qaic/
H A D	qaic.rst	111 This IOCTL allows userspace to allocate a buffer object (BO) which can send 113 represents the allocated buffer. The BO is not usable until it has been 117 This IOCTL allows userspace to prepare an allocated BO to be mmap'd into the 121 This IOCTL allows userspace to slice a BO in preparation for sending the BO 122 to the device. Slicing is the operation of describing what portions of a BO 124 DMA Bridge, and as such, locks the BO to a specific DBC. 133 to shrink the BOs sent to the device for this specific call. If a BO 135 allows userspace to indicate that only the first M bytes of the BO should be 141 This IOCTL allows userspace to determine when a particular BO has been 142 processed by the device. The call will block until either the BO has been [all …]
/linux/Documentation/gpu/
H A D	v3d.rst	`8 GPU buffer object (BO) management 12 :doc: V3D GEM BO management support`
H A D	vc4.rst	`81 GPU buffer object (BO) management 85 :doc: VC4 GEM BO management support`
H A D	i915.rst	303 `GEM BO Management Implementation Details`_. 337 the GPU address when a GEM BO is assigned a GPU address and the kernel 338 might evict a different GEM BO from the (PP)GTT to make address room 339 for another GEM BO. Consequently, the ioctls submitting a batchbuffer 390 GEM BO Management Implementation Details
H A D	drm-vm-bind-async.rst	`242 * operations, the BO handle MBZ, and the BO offset MBZ. This flag is`
H A D	todo.rst	`190 private lock. The tricky part is the BO free functions, since those can't`
/linux/Documentation/gpu/rfc/
H A D	i915_vm_bind.rst	29 * VA mapping can map to a partial section of the BO (partial binding). 84 VM_BIND feature introduces an optimization where user can create BO which 86 BO creation. Unlike Shared BOs, these VM private BOs can only be mapped on 182 invalidation, revalidate the BO and then resume the compute context. This is 220 VM_BIND allows any hints setting per mapping instead of per BO. Possible hints 221 include placement and atomicity. Sub-BO level placement hint will be even more 226 VM_BIND allows cache/CLOS settings per mapping instead of per BO. 238 VM_BIND interface can be used to map system memory directly (without gem BO
H A D	i915_small_bar.rst	`12 New gem_create_ext flag to tell the kernel that a BO will require CPU access.`
/linux/Documentation/gpu/xe/
H A D	xe_mm.rst	`8 :doc: Buffer Objects (BO)`
/linux/drivers/gpu/drm/ttm/tests/
H A D	TODO	`4 - Add a test case where the only evictable BO is busy`
/linux/drivers/accel/ivpu/
H A D	ivpu_gem.c	`27 ivpu_dbg(vdev, BO, in ivpu_dbg_bo()`
/linux/arch/powerpc/xmon/
H A D	ppc-opc.c	220 #define BO BFA + 1 macro 226 #define BOE BO + 1 4125 {"bc", B(16,0,0), B_MASK, COM, PPCVLE, {BO, BI, BD}}, 4128 {"bcl", B(16,0,1), B_MASK, COM, PPCVLE, {BO, BI, BD}}, 4131 {"bca", B(16,1,0), B_MASK, COM, PPCVLE, {BO, BI, BDA}}, 4134 {"bcla", B(16,1,1), B_MASK, COM, PPCVLE, {BO, BI, BDA}}, 4371 {"bclr", XLLK(19,16,0), XLBH_MASK, PPCCOM, PPCVLE, {BO, BI, BH}}, 4372 {"bcr", XLLK(19,16,0), XLBB_MASK, PWRCOM, PPCVLE, {BO, BI}}, 4373 {"bclrl", XLLK(19,16,1), XLBH_MASK, PPCCOM, PPCVLE, {BO, BI, BH}}, 4374 {"bcrl", XLLK(19,16,1), XLBB_MASK, PWRCOM, PPCVLE, {BO, BI}}, [all …]