v2: - lots of changes according to Emil Velikov's comments - implemented radeon_winsys::read_registers v3: - a lot of new work, many of them adapt to libdrm interface changes Squashed patches: winsys/amdgpu: implement radeon_winsys context support winsys/amdgpu: add reference counting for contexts winsys/amdgpu: add userptr support winsys/amdgpu: allocate IBs like normal buffers winsys/amdgpu: add IBs to the buffer list, adapt to interface changes winsys/amdgpu: don't use KMS handles as reloc hash keys winsys/amdgpu: sync buffer accesses to different rings winsys/amdgpu: use dependencies instead of waiting for last fence v2 gallium/radeon: unify buffer_wait and buffer_is_busy in the winsys interface (amdgpu part) winsys/amdgpu: track fences per ring and be thread-safe winsys/amdgpu: simplify waiting on a variable in amdgpu_fence_wait gallium/radeon: allow the winsys to choose the IB size (amdgpu part) winsys/amdgpu: switch to new amdgpu_cs_query_fence_status interface winsys/amdgpu: handle fence and dependencies merge winsys/amdgpu follow libdrm change to move user fence into UMD winsys/amdgpu: use amdgpu_bo_va_op for va map/unmap v2 winsys/amdgpu: use the new tiling flags winsys/amdgpu: switch to new GTT_USWC definition winsys/amdgpu: expose amdgpu_cs_query_reset_state to drivers winsys/amdgpu: fix valgrind warnings winsys/amdgpu: don't use VRAM with APUs that don't have much of it winsys/amdgpu: require LLVM 3.6.1 for VI because of bug fixes there winsys/amdgpu: remove amdgpu_winsys::num_cpus winsys/amdgpu: align BO size to page size winsys/amdgpu: reduce BO cache timeout winsys/amdgpu: remove useless flushing and waiting in amdgpu_bo_set_tiling winsys/amdgpu: use amdgpu_device_handle as a unique device ID instead of fd winsys/amdgpu: use safer access to amdgpu_fence_wait::signalled winsys/amdgpu: allow maximum IB size of 4 MB winsys/amdgpu: add ip_instance into amdgpu_fence gallium/radeon: add RING_COMPUTE instead of RADEON_FLUSH_COMPUTE winsys/amdgpu: set the ring type at CS initilization winsys/amdgpu: query the GART page size from the kernel winsys/amdgpu: correctly wait for shared buffers to become idle winsys/amdgpu: set the amdgpu_cs_fence structure only once at fence creation winsys/amdgpu: add a specific error message for cs_submit -> -ENOMEM winsys/amdgpu: check num_active_ioctls before calling amdgpu_bo_wait_for_idle winsys/amdgpu: clear user fence BO after allocating it winsys/amdgpu: fix user fences winsys/amdgpu: make amdgpu_winsys_create public winsys/amdgpu: remove thread offloading winsys/amdgpu: flatten the amdgpu_cs_context structure and simplify more v4: require libdrm 2.4.63 |
||
---|---|---|
.. | ||
auxiliary | ||
docs | ||
drivers | ||
include | ||
state_trackers | ||
targets | ||
tests | ||
tools | ||
winsys | ||
Android.common.mk | ||
Android.mk | ||
Automake.inc | ||
Makefile.am | ||
README.portability | ||
SConscript |
README.portability
CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D = General Considerations = The state tracker and winsys driver support a rather limited number of platforms. However, the pipe drivers are meant to run in a wide number of platforms. Hence the pipe drivers, the auxiliary modules, and all public headers in general, should strictly follow these guidelines to ensure = Compiler Support = * Include the p_compiler.h. * Cast explicitly when converting to integer types of smaller sizes. * Cast explicitly when converting between float, double and integral types. * Don't use named struct initializers. * Don't use variable number of macro arguments. Use static inline functions instead. * Don't use C99 features. = Standard Library = * Avoid including standard library headers. Most standard library functions are not available in Windows Kernel Mode. Use the appropriate p_*.h include. == Memory Allocation == * Use MALLOC, CALLOC, FREE instead of the malloc, calloc, free functions. * Use align_pointer() function defined in u_memory.h for aligning pointers in a portable way. == Debugging == * Use the functions/macros in p_debug.h. * Don't include assert.h, call abort, printf, etc. = Code Style = == Inherantice in C == The main thing we do is mimic inheritance by structure containment. Here's a silly made-up example: /* base class */ struct buffer { int size; void (*validate)(struct buffer *buf); }; /* sub-class of bufffer */ struct texture_buffer { struct buffer base; /* the base class, MUST COME FIRST! */ int format; int width, height; }; Then, we'll typically have cast-wrapper functions to convert base-class pointers to sub-class pointers where needed: static inline struct vertex_buffer *vertex_buffer(struct buffer *buf) { return (struct vertex_buffer *) buf; } To create/init a sub-classed object: struct buffer *create_texture_buffer(int w, int h, int format) { struct texture_buffer *t = malloc(sizeof(*t)); t->format = format; t->width = w; t->height = h; t->base.size = w * h; t->base.validate = tex_validate; return &t->base; } Example sub-class method: void tex_validate(struct buffer *buf) { struct texture_buffer *tb = texture_buffer(buf); assert(tb->format); assert(tb->width); assert(tb->height); } Note that we typically do not use typedefs to make "class names"; we use 'struct whatever' everywhere. Gallium's pipe_context and the subclassed psb_context, etc are prime examples of this. There's also many examples in Mesa and the Mesa state tracker.