mesa/src/intel/isl
Kenneth Graunke 0b44644ca6 genxml: Consistently use a numeric "MOCS" field
When we first started using genxml, we decided to represent MOCS as an
actual structure, and pack values.  However, in many places, it was more
convenient to use a numeric value rather than treating it as a struct,
so we added secondary setters in a bunch of places as well.

We were not entirely consistent, either.  Some places only had one.
Gen6 had both kinds of setters for STATE_BASE_ADDRESS, but newer gens
only had the struct-based setters.  The names were sometimes "Constant
Buffer Object Control State" instead of "Memory", making it harder to
find.  Many had prefixes like "Vertex Buffer MOCS"...in a vertex buffer
packet...which is a bit redundant.

On modern hardware, MOCS is simply an index into a table, but we were
still carrying around the structure with an "Index to MOCS Table" field,
in addition to the direct numeric setters.  This is clunky - we really
just want a number on new hardware.

This patch eliminates the struct-based setters, and makes the numeric
setters be consistently called "MOCS".  We leave the struct definition
around on Gen7-8 for reference purposes, but it is unused.

v2: Drop bonus "Depth Buffer MOCS" fields on Gen7.5 and Gen9

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com>
2018-12-14 00:44:54 -08:00
..
tests intel/isl: Add a unit suffixes to some struct fields and variables 2018-09-26 08:52:26 -05:00
.gitignore Move isl to src/intel 2016-02-18 10:34:47 -08:00
gen_format_layout.py intel: various python cleanups 2018-08-16 17:38:25 +01:00
isl.c intel/isl: Add a unit suffixes to some struct fields and variables 2018-09-26 08:52:26 -05:00
isl.h intel/isl: Add a unit suffixes to some struct fields and variables 2018-09-26 08:52:26 -05:00
isl_drm.c intel: Split gen_device_info out into libintel_dev 2018-03-05 09:47:37 -08:00
isl_emit_depth_stencil.c genxml: Consistently use a numeric "MOCS" field 2018-12-14 00:44:54 -08:00
isl_format.c intel/isl: Add bounds-checking assertions for the format_info table 2018-06-07 11:23:34 -07:00
isl_format_layout.csv i965: Correct L8_UNORM_SRGB table entry 2018-11-19 08:05:44 +01:00
isl_gen4.c intel/isl/gen4: Make depth/stencil buffers Y-Tiled 2018-07-19 11:05:07 -07:00
isl_gen4.h intel/isl: Add gen4_filter_tiling 2017-05-26 07:58:01 -07:00
isl_gen6.c intel/isl/gen6: Fix combined depth stencil alignment 2017-05-16 17:04:26 -07:00
isl_gen6.h isl: use ifndef header guards 2016-10-14 11:53:32 +01:00
isl_gen7.c intel/isl: Avoid tiling some 16K-wide render targets 2018-08-22 13:53:19 -07:00
isl_gen7.h isl: use ifndef header guards 2016-10-14 11:53:32 +01:00
isl_gen8.c intel/isl: Refactor gen8_choose_image_alignment_el 2017-05-16 17:04:26 -07:00
isl_gen8.h isl: use ifndef header guards 2016-10-14 11:53:32 +01:00
isl_gen9.c isl: prefix non-static API with isl_ 2016-10-14 11:53:22 +01:00
isl_gen9.h isl: use ifndef header guards 2016-10-14 11:53:32 +01:00
isl_genX_priv.h isl: Add a null surface fill function. 2017-08-19 00:46:36 -07:00
isl_priv.h intel: Split gen_device_info out into libintel_dev 2018-03-05 09:47:37 -08:00
isl_storage_image.c intel/isl: Add a unit suffixes to some struct fields and variables 2018-09-26 08:52:26 -05:00
isl_surface_state.c intel/isl: Add a unit suffixes to some struct fields and variables 2018-09-26 08:52:26 -05:00
meson.build meson: Add tests to suites 2018-11-20 09:09:22 -08:00
README Move isl to src/intel 2016-02-18 10:34:47 -08:00

Intel Surface Layout

Introduction
============
isl is a small library that calculates the layout of Intel GPU surfaces, queries
those layouts, and queries the properties of surface formats.


Independence from User APIs
===========================
isl's API is independent of any user-facing graphics API, such as OpenGL and
Vulkan. This independence allows isl to be used a shared component by multiple
Intel drivers.

Rather than mimic the user-facing APIs, the isl API attempts to reflect Intel
hardware: the actual memory layout of Intel GPU surfaces and how one programs
the GPU to use those surfaces. For example:

  - The tokens of `enum isl_format` (such as `ISL_FORMAT_R8G8B8A8_UNORM`)
    match those of the hardware enum `SURFACE_FORMAT` rather than the OpenGL
    or Vulkan format tokens.  And the values of `isl_format` and
    `SURFACE_FORMAT` are identical.

  - The OpenGL and Vulkan APIs contain depth and stencil formats. However the
    hardware enum `SURFACE_FORMAT` does not, and therefore neither does `enum
    isl_format`. Rather than define new pixel formats that have no hardware
    counterpart, isl records the intent to use a surface as a depth or stencil
    buffer with the usage flags `ISL_SURF_USAGE_DEPTH_BIT` and
    `ISL_SURF_USAGE_STENCIL_BIT`.

  - `struct isl_surf` distinguishes between the surface's logical dimension
    from the user API's perspective (`enum isl_surf_dim`, which may be 1D, 2D,
    or 3D) and the layout of those dimensions in memory (`enum isl_dim_layout`).


Surface Units
=============

Intro
-----
ISL takes care in its equations to correctly handle conversion among surface
units (such as pixels and compression blocks) and to carefully distinguish
between a surface's logical layout in the client API and its physical layout
in memory.

Symbol names often explicitly declare their unit with a suffix:

   - px: logical pixels
   - sa: physical surface samples
   - el: physical surface elements
   - sa_rows: rows of physical surface samples
   - el_rows: rows of physical surface elements

Logical units are independent of hardware generation and are closely related
to the user-facing API (OpenGL and Vulkan). Physical units are dependent on
hardware generation and reflect the surface's layout in memory.

Definitions
-----------
- Logical Pixels (px):

  The surface's layout from the perspective of the client API (OpenGL and
  Vulkan) is in units of logical pixels. Logical pixels are independent of the
  surface's layout in memory.

  A surface's width and height, in units of logical pixels, is not affected by
  the surface's sample count. For example, consider a VkImage created with
  VkImageCreateInfo{width=w0, height=h0, samples=s0}. The surface's width and
  height at level 0 is, in units of logical pixels, w0 and h0 regardless of
  the value of s0.

  For example, the logical array length of a 3D surface is always 1, even on
  Gen9 where the surface's memory layout is that of an array surface
  (ISL_DIM_LAYOUT_GEN4_2D).

- Physical Surface Samples (sa):

  For a multisampled surface, this unit has the obvious meaning.
  A singlesampled surface, from ISL's perspective, is simply a multisampled
  surface whose sample count is 1.

  For example, consider a 2D single-level non-array surface with samples=4,
  width_px=64, and height_px=64 (note that the suffix 'px' indicates logical
  pixels). If the surface's multisample layout is ISL_MSAA_LAYOUT_INTERLEAVED,
  then the extent of level 0 is, in units of physical surface samples,
  width_sa=128, height_sa=128, depth_sa=1, array_length_sa=1. If
  ISL_MSAA_LAYOUT_ARRAY, then width_sa=64, height_sa=64, depth_sa=1,
  array_length_sa=4.

- Physical Surface Elements (el):

  This unit allows ISL to treat compressed and uncompressed formats
  identically in many calculations.

  If the surface's pixel format is compressed, such as ETC2, then a surface
  element is equivalent to a compression block. If uncompressed, then
  a surface element is equivalent to a surface sample. As a corollary, for
  a given surface a surface element is at least as large as a surface sample.

Errata
------
ISL acquired the term 'surface element' from the Broadwell PRM [1], which
defines it as follows:

   An element is defined as a pixel in uncompresed surface formats, and as
   a compression block in compressed surface formats. For MSFMT_DEPTH_STENCIL
   type multisampled surfaces, an element is a sample.


References
==========
[1]: Broadwell PRM >> Volume 2d: Command Reference: Structures >>
     RENDER_SURFACE_STATE Surface Vertical Alignment (p325)