mesa/src/gallium
Nicolai Hähnle 75affd73b0 radeonsi: re-order the perfcounter hardware blocks
As documented in the comment, AMD GPUPerfStudio unfortunately hardcodes the
order of performance counter groups. Let's do the pragmatic thing and present
the same order as Catalyst/Crimson.

Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Acked-by: Marek Olšák <marek.olsak@amd.com>
2016-02-05 09:25:27 -05:00
..
auxiliary st/nine: Fix use of uninitialized memory 2016-02-04 22:12:17 +01:00
docs gallium: add PIPE_CAP_QUERY_BUFFER_OBJECT 2016-02-04 21:21:30 -05:00
drivers radeonsi: re-order the perfcounter hardware blocks 2016-02-05 09:25:27 -05:00
include gallium: add PIPE_CAP_QUERY_BUFFER_OBJECT 2016-02-04 21:21:30 -05:00
state_trackers st/nine: Use align_free when needed 2016-02-04 22:12:17 +01:00
targets DRI_CONFIG: Add option to override vendor id 2016-02-04 22:12:17 +01:00
tests gallium/tests: fix build with clang compiler 2016-01-03 12:18:00 +01:00
tools
winsys winsys/radeon: Do not deinit the pb cache if it was not initialized 2016-02-02 21:11:15 +01:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk virgl: also build vtest for Android 2016-02-02 09:58:51 +10:00
Automake.inc gallium: keep the libdrm link alongside libkmsdri.la 2015-11-21 12:52:18 +00:00
Makefile.am automake: remove no longer needed HAVE_LOADER_GALLIUM conditional 2015-11-21 12:52:19 +00:00
README.portability gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
SConscript pipe-loader: add preliminary scons support 2015-11-21 12:52:20 +00:00

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.