Documentation patch for batchbuffer submission
Subsystems (4)
v3 cover Documentation patch for batchbuffer submission
From: Kevin Rogovin <[email protected]>
Note: I want to make a one or two follow-up series that provide narration and potentially additional documentation for GUC submission and the breadcrumbs.
v3:
More documentation: emphasize that handling of batchbuffer requests creates a request struct that is added to the dependency tree and that the inform to the hardware that there is new data on a ringbuffer is deferred until dependencies are satsified.
Break patch into more digestable chunks.
v2:
More documentation: intel_ringbuffer, sequence number. Expose to i915.rst existing documentation
Call out GEM_EXECBUFFER as deprecated.
Place code detailed documentation in source files. Call out INTEL_EXEC_RENDER.
Reorder text to make it more readable.
Refer to Command Buffer Parser instead of Batchbuffer Parser. (suggested by Joonas Lahtinen)
Kevin Rogovin (6):
i915.rst: Narration overview on GEM + minor reorder to improve
narration
i915.rst: rename section Batchbuffer Parsing to Command Buffer Parsing
i915: add documentation of what happens at the bottom of submitting a
batchbuffer
i915: add documentation for a bit on batchbuffer submission backend
i915: add doc for synchronization
i915.rst: narration for batchbuffer submission + links to source code
doc entries on the subject
Documentation/gpu/i915.rst | 189 ++++++++++++++++++++++++++------ drivers/gpu/drm/i915/i915_request.h | 28 +++++ drivers/gpu/drm/i915/i915_vma.h | 10 +- drivers/gpu/drm/i915/intel_ringbuffer.h | 71 ++++++++++++ 4 files changed, 262 insertions(+), 36 deletions(-)
Signature · 6 lines
2.16.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 1/5 i915.rst: Narration overview on GEM + minor reorder to improve narration
From: Kevin Rogovin <[email protected]>
--- Documentation/gpu/i915.rst | 129 +++++++++++++++++++++++++++++++++------- drivers/gpu/drm/i915/i915_vma.h | 10 +++- 2 files changed, 113 insertions(+), 26 deletions(-)
Documentation/gpu/i915.rst +106 -23
@@ -249,6 +249,112 @@ Memory Management and Command Submission This sections covers all things related to the GEM implementation in the i915 driver. +Intel GPU Basics +---------------- + +An Intel GPU has multiple engines. There are several engine types. +The user-space value `I915_EXEC_DEFAULT` is an alias to the user +space value `I915_EXEC_RENDER`. + +- RCS engine is for rendering 3D and performing compute, this is named `I915_EXEC_RENDER` in user space. +- BCS is a blitting (copy) engine, this is named `I915_EXEC_BLT` in user space. +- VCS is a video encode and decode engine, this is named `I915_EXEC_BSD` in user space +- VECS is video enhancement engine, this is named `I915_EXEC_VEBOX` in user space. + +The Intel GPU family is a familiy of integrated GPU's using Unified +Memory Access. For having the GPU "do work", user space will feed the +GPU batch buffers via one of the ioctls `DRM_IOCTL_I915_GEM_EXECBUFFER2` +or `DRM_IOCTL_I915_GEM_EXECBUFFER2_WR` (the ioctl `DRM_IOCTL_I915_GEM_EXECBUFFER` +is deprecated). Most such batchbuffers will instruct the GPU to perform +work (for example rendering) and that work needs memory from which to +read and memory to which to write. All memory is encapsulated within GEM +buffer objects (usually created with the ioctl `DRM_IOCTL_I915_GEM_CREATE`). +An ioctl providing a batchbuffer for the GPU to create will also list +all GEM buffer objects that the batchbuffer reads and/or writes. For +implementation details of memory management see +`GEM BO Management Implementation Details`_. + +A GPU pipeline (mostly strongly so for the RCS engine) has a great deal +of state which is to be programmed by user space via the contents of a +batchbuffer. Starting in Gen6 (SandyBridge), hardware contexts are +supported. A hardware context encapsulates GPU pipeline state and other +portions of GPU state and it is much more efficient for the GPU to load +a hardware context instead of re-submitting commands in a batchbuffer to +the GPU to restore state. In addition, using hardware contexts provides +much better isolation between user space clients. The ioctl +`DRM_IOCTL_I915_GEM_CONTEXT_CREATE` is used by user space to create a +hardware context which is identified by a 32-bit integer. The +non-deprecated ioctls to submit batchbuffer work can pass that ID (in +the lower bits of drm_i915_gem_execbuffer2::rsvd1) to identify what HW +context to use with the command. When the kernel submits the batchbuffer +to be executed by the GPU it will also instruct the GPU to load the HW +context prior to executing the contents of a batchbuffer. + +The GPU has its own memory management and address space. The kernel +driver maintains the memory translation table for the GPU. For older +GPUs (i.e. those before Gen8), there is a single global such translation +table, a global Graphics Translation Table (GTT). For newer generation +GPUs each hardware context has its own translation table, called +Per-Process Graphics Translation Table (PPGTT). Of important note, is +that although PPGTT is named per-process it is actually per hardware +context. When user space submits a batchbuffer, the kernel walks the +list of GEM buffer objects used by the batchbuffer and guarantees that +not only is the memory of each such GEM buffer object resident but it +is also present in the (PP)GTT. If the GEM buffer object is not yet +placed in the (PP)GTT, then it is given an address. Two consequences +of this are: the kernel needs to edit the batchbuffer submitted to +write the correct value of the GPU address when a GEM BO is assigned a +GPU address and the kernel might evict a different GEM BO from the +(PP)GTT to make address room for a GEM BO. + +Consequently, the ioctls submitting a batchbuffer for execution also +include a list of all locations within buffers that refer to +GPU-addresses so that the kernel can edit the buffer correctly. This +process is dubbed relocation. The ioctls allow user space to provide to +the kernel a presumed offset for each GEM buffer object used in a +batchbuffer. If the kernel sees that the address provided by user space +is correct, then it skips performing relocation for that GEM buffer +object. In addition, the kernel provides to what addresses the kernel +relocates each GEM buffer object. + +There is also an interface for user space to directly specify the +address location of GEM BO's, the feature soft-pinning and made active +within an execbuffer2 ioctl with `EXEC_OBJECT_PINNED` bit up. If +user-space also specifies `I915_EXEC_NO_RELOC`, then the kernel is to +not execute any relocation and user-space manages the address space for +its PPGTT itself. The advantage of user space handling address space is +that then the kernel does far less work and user space can safely assume +that GEM buffer object's location in GPU address space do not change. + +GEM BO Management Implementation Details +---------------------------------------- + +.. kernel-doc:: drivers/gpu/drm/i915/i915_vma.h + :doc: Virtual Memory Address + +Buffer Object Eviction +---------------------- + +This section documents the interface functions for evicting buffer +objects to make space available in the virtual gpu address spaces. Note +that this is mostly orthogonal to shrinking buffer objects caches, which +has the goal to make main memory (shared with the gpu through the +unified memory architecture) available. + +.. kernel-doc:: drivers/gpu/drm/i915/i915_gem_evict.c + :internal: + +Buffer Object Memory Shrinking +------------------------------ + +This section documents the interface function for shrinking memory usage +of buffer object caches. Shrinking is used to make main memory +available. Note that this is mostly orthogonal to evicting buffer +objects, which has the goal to make space in gpu virtual address spaces. + +.. kernel-doc:: drivers/gpu/drm/i915/i915_gem_shrinker.c + :internal: + Batchbuffer Parsing -------------------
@@ -312,29 +418,6 @@ Object Tiling IOCTLs .. kernel-doc:: drivers/gpu/drm/i915/i915_gem_tiling.c :doc: buffer object tiling -Buffer Object Eviction ----------------------- - -This section documents the interface functions for evicting buffer -objects to make space available in the virtual gpu address spaces. Note -that this is mostly orthogonal to shrinking buffer objects caches, which -has the goal to make main memory (shared with the gpu through the -unified memory architecture) available. - -.. kernel-doc:: drivers/gpu/drm/i915/i915_gem_evict.c - :internal: - -Buffer Object Memory Shrinking ------------------------------- - -This section documents the interface function for shrinking memory usage -of buffer object caches. Shrinking is used to make main memory -available. Note that this is mostly orthogonal to evicting buffer -objects, which has the goal to make space in gpu virtual address spaces. - -.. kernel-doc:: drivers/gpu/drm/i915/i915_gem_shrinker.c - :internal: - GuC ===
drivers/gpu/drm/i915/i915_vma.h +7 -3
@@ -38,9 +38,13 @@enum i915_cache_level ;/** -* A VMA represents a GEM BO that is bound into an address space. Therefore, a -* VMA's presence cannot be guaranteed before binding, or after unbinding the -* object into/from the address space. +* DOC: Virtual Memory Address +* +* An `i915_vma` struct represents a GEM BO that is bound into an address +* space. Therefore, a VMA's presence cannot be guaranteed before binding, or +* after unbinding the object into/from the address space. The struct includes +* the bookkepping details needed for tracking it in all the lists with which +* it interacts. * * To make things as simple as possible (ie. no refcounting), a VMA's lifetime * will always be <= an objects lifetime. So object refcounting should cover us.
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 2/5 i915: add documentation of what happens at the bottom of submitting a batchbuffer
In reply to [email protected]From: Kevin Rogovin <[email protected]>
--- drivers/gpu/drm/i915/intel_ringbuffer.h | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+)
drivers/gpu/drm/i915/intel_ringbuffer.h +33 -0
@@ -317,6 +317,39 @@ struct intel_engine_execlists {#define INTEL_ENGINE_CS_MAX_NAME 8 +/** +* DOC: Ringbuffers to submit batchbuffers +* +* At the lowest level, submitting work to a GPU engine is to add commands to +* a ringbuffer. A ringbuffer in the kernel driver is essentially a location +* from which the GPU reads its next command. To avoid copying the contents +* of a batchbuffer in order to submit it, the GPU has native hardware support +* to perform commands specified in another buffer; the command to do so is +* a batchbuffer start and the i915 kernel driver uses this to avoid copying +* batchbuffers to the ringbuffer. At the very bottom of the stack, the i915 +* does the following to submit a batchbuffer to the GPU. +* +* 1. Add a command to invalidate caches to the ringbuffer +* +* 2. Add a batchbuffer start command to the ringbuffer. The start command is +* essentially a token together with the GPU address of the batchbuffer to +* be executed. +* +* 3. Add a pipeline flush to the the ringbuffer. +* +* 4. Add a register write command to the ring buffer. This register write +* writes the the request ID, ``i915_request::global_seqno``; the i915 +* kernel driver uses the value in the register to know what requests are +* completed. +* +* 5. Add a user interrupt command to the ringbuffer. This command instructs +* the GPU to issue an interrupt when the command (and pipeline flush) are +* completed. +* +* 6. Inform the hardware of the additional commands added to +* the ringbuffer. +*/ +struct intel_engine_cs {struct drm_i915_private *i915;char name[INTEL_ENGINE_CS_MAX_NAME ];
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 3/5 i915: add documentation for a bit on batchbuffer submission backend
In reply to [email protected]From: Kevin Rogovin <[email protected]>
--- drivers/gpu/drm/i915/intel_ringbuffer.h | 38 +++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+)
drivers/gpu/drm/i915/intel_ringbuffer.h +38 -0
@@ -350,6 +350,44 @@ struct intel_engine_execlists {* the ringbuffer. */ +/** +* DOC: Batchbuffer Submission Backend +* +* The core logic of submitting a batchbuffer for the GPU to execute +* is shared across all engines for all GPU generations. Through the use +* of functions pointers, we can customize submission to different GPU +* capabilities. The struct ``intel_engine_cs`` has the following member +* function pointers for the following purposes in the scope of batchbuffer +* submission. +* +* - context_pin +* pins the context and also returns to what ``intel_ringbuffer`` +* to write to submit a batchbuffer. +* +* - request_alloc +* is used to reserve space in an ``intel_ringbuffer`` +* for submitting a batchbuffer to the GPU. +* +* - emit_flush +* writes a pipeline flush command and/or invalidate caches +* command to the ring buffer. +* +* - emit_bb_start +* writes the batchbuffer start command to the ringer buffer. +* +* - emit_breadcrumb +* writes to the ring buffer both the regiser write of the +* request ID (`i915_request::global_seqno`) and the command to +* issue an interrupt. +* +* - submit_request +* See the comment on this member in ``intel_engine_cs``, declared +* in intel_ringbuffer.h. +* +* In addition, the struct i915_request is used to track requests' +* dependency tree. +*/ +struct intel_engine_cs {struct drm_i915_private *i915;char name[INTEL_ENGINE_CS_MAX_NAME ];
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 4/5 i915: add doc for synchronization
In reply to [email protected]From: Kevin Rogovin <[email protected]>
--- drivers/gpu/drm/i915/i915_request.h | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+)
drivers/gpu/drm/i915/i915_request.h +28 -0
@@ -57,6 +57,34 @@ struct i915_dependency {#define I915_DEPENDENCY_ALLOC BIT(0) }; +/** +* DOC: Synchronization +* +* The i915 kernel driver needs to also synchronize the ordering in which +* to submit batchbuffers in following cases. +* +* 1. When a fixed file descriptor is used to submit work to different +* engines of the GPU; the issue is that the different engines run +* independently to each other but the kernel interface guarantees +* that the memory writes of previously issued commands within a +* fixed file descriptor will be seen by the next command. +* +* 2. When an ioctl to submit a batchbuffer has an in-fence that represents +* an action that needs to be completed or submitted before before the +* given command is submitted. +* +* Rather than waiting, the i915 kernel driver builds a data structure tree +* (represented by ``i915_priotree``) to store dependencies of different +* batchbuffer execute requests, the requests themselves are tracked via +* ``i915_request`` structs. The critical point that action of processing +* a user request does NOT wait for the dependencies to finish or even be +* submitted to the GPU. Instead, an ``i915_request`` structure is created +* and it is added to the dependency tree; when its dependencies are +* satisfied, then the call back updates the tail pointer of the ring buffer +* where the command was placed. This way, execute batchbuffer requests +* return from the kernel almost immediately. +*/ +/* * "People assume that time is a strict progression of cause to effect, but * actually, from a nonlinear, non-subjective viewpoint, it's more like a big
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 5/5 i915.rst: narration for batchbuffer submission + links to source code doc entries on the subject
In reply to [email protected]From: Kevin Rogovin <[email protected]>
--- Documentation/gpu/i915.rst | 58 +++++++++++++++++++++++++++++++++++++++------- 1 file changed, 49 insertions(+), 9 deletions(-)
Documentation/gpu/i915.rst +49 -9
@@ -355,6 +355,55 @@ objects, which has the goal to make space in gpu virtual address spaces. .. kernel-doc:: drivers/gpu/drm/i915/i915_gem_shrinker.c :internal: +Batchbuffer Submission +---------------------- + +Depending on GPU generation, the i915 kernel driver will submit batchbuffers +in one of the several ways. However, the top code logic is shared for all +methods, see `Common: At the bottom`_ and `Common: Processing requests`_ +for details. In addition, the kernel may filter the contents of user space +provided batchbuffers. To that end the i915 driver has a +`Batchbuffer Parsing`_ and a pool from which to allocate buffers to place +filtered user space batchbuffers, see section `Batchbuffer Pools`_. + +Common: At the bottom +~~~~~~~~~~~~~~~~~~~~~ + +.. kernel-doc:: drivers/gpu/drm/i915/intel_ringbuffer.h + :doc: Ringbuffers to submit batchbuffers + +Common: Synchronization +~~~~~~~~~~~~~~~~~~~~~~~ + +.. kernel-doc:: drivers/gpu/drm/i915/i915_request.h + :doc: Synchronization + +Common: Processing requests +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. kernel-doc:: drivers/gpu/drm/i915/i915_gem_execbuffer.c + :doc: User command execution + +Batchbuffer Submission Varieties +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. kernel-doc:: drivers/gpu/drm/i915/intel_ringbuffer.h + :doc: Batchbuffer Submission Backend + +The two varieties for submitting batchbuffer to the GPU are the following. + +1. Batchbuffers are subbmitted directly to a ring buffer; this is the most basic way to submit batchbuffers to the GPU and is for generations strictly before Gen8. +2. Batchbuffer are submitting via execlists are a features supported by Gen8 and new devices; the macro :c:macro:'HAS_EXECLISTS' is used to determine if a GPU supports submitting via execlists, see `Logical Rings, Logical Ring Contexts and Execlists`_. + +Logical Rings, Logical Ring Contexts and Execlists +-------------------------------------------------- + +.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c + :doc: Logical Rings, Logical Ring Contexts and Execlists + +.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c + :internal: + Batchbuffer Parsing -------------------
@@ -373,15 +422,6 @@ Batchbuffer Pools .. kernel-doc:: drivers/gpu/drm/i915/i915_gem_batch_pool.c :internal: -Logical Rings, Logical Ring Contexts and Execlists --------------------------------------------------- - -.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c - :doc: Logical Rings, Logical Ring Contexts and Execlists - -.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c - :internal: - Global GTT views ----------------
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting [email protected] (2018-03-27 11:26:14)
Quoted 13 lines
From: Kevin Rogovin <[email protected]>
Note: I want to make a one or two follow-up series that provide narration and potentially additional documentation for GUC submission and the breadcrumbs.
v3:
More documentation: emphasize that handling of batchbuffer requests creates a request struct that is added to the dependency tree and that the inform to the hardware that there is new data on a ringbuffer is deferred until dependencies are satsified.
Quoted 7 lines
Break patch into more digestable chunks.
v2:
More documentation:intel_ringbuffer, sequence number. Expose toi915.rstexisting documentationCall out
GEM_EXECBUFFERas deprecated.
Oh not it isn't. _WR has a singular purpose that isn't even the recommend method any more.
-Chris
_______________________________________________
Intel-gfx mailing list [email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
Quoted 3 lines
Quoted 1 line
Call out
GEM_EXECBUFFERas deprecated.Oh not it isn't.
_WRhas a singular purpose that isn't even the recommend method any more.
I had understood that DRM_I915_GEM_EXECBUFFER was considered deprecated. I will fix this mistake on next spin.
I had thought that DRM_i915_GEM_EXECBUFFER2_WR is needed in order to return an out fence to user space (Mesa/i965 uses it for the out fence) What is the recommended way to do out fence? Or is the way for user space to do synchro's a different way than fences? I will also fix this in the next spin.
-Kevin
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for Documentation patch for batchbuffer submission (rev3)
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Documentation patch for batchbuffer submission (rev3)
URL : https://patchwork.freedesktop.org/series/38433/
State : success
== Summary ==
Series 38433v3 Documentation patch for batchbuffer submission
https://patchwork.freedesktop.org/api/1.0/series/38433/revisions/3/mbox/
fi-bdw-5557u total:285 pass:264 dwarn:0 dfail:0 fail:0 skip:21 time:439s fi-bdw-gvtdvm total:285 pass:261 dwarn:0 dfail:0 fail:0 skip:24 time:442s fi-blb-e6850 total:285 pass:220 dwarn:1 dfail:0 fail:0 skip:64 time:382s fi-bsw-n3050 total:285 pass:239 dwarn:0 dfail:0 fail:0 skip:46 time:538s fi-bwr-2160 total:285 pass:180 dwarn:0 dfail:0 fail:0 skip:105 time:297s fi-bxt-j4205 total:285 pass:256 dwarn:0 dfail:0 fail:0 skip:29 time:516s fi-byt-j1900 total:285 pass:250 dwarn:0 dfail:0 fail:0 skip:35 time:523s fi-byt-n2820 total:285 pass:246 dwarn:0 dfail:0 fail:0 skip:39 time:511s fi-cfl-8700k total:285 pass:257 dwarn:0 dfail:0 fail:0 skip:28 time:413s fi-cfl-s3 total:285 pass:259 dwarn:0 dfail:0 fail:0 skip:26 time:566s fi-cfl-u total:285 pass:259 dwarn:0 dfail:0 fail:0 skip:26 time:512s fi-cnl-y3 total:285 pass:259 dwarn:0 dfail:0 fail:0 skip:26 time:583s fi-elk-e7500 total:285 pass:225 dwarn:1 dfail:0 fail:0 skip:59 time:428s fi-gdg-551 total:285 pass:176 dwarn:0 dfail:0 fail:1 skip:108 time:321s fi-hsw-4770 total:285 pass:258 dwarn:0 dfail:0 fail:0 skip:27 time:403s fi-ilk-650 total:285 pass:225 dwarn:0 dfail:0 fail:0 skip:60 time:422s fi-ivb-3520m total:285 pass:256 dwarn:0 dfail:0 fail:0 skip:29 time:468s fi-ivb-3770 total:285 pass:252 dwarn:0 dfail:0 fail:0 skip:33 time:430s fi-kbl-7500u total:285 pass:260 dwarn:1 dfail:0 fail:0 skip:24 time:475s fi-kbl-7567u total:285 pass:265 dwarn:0 dfail:0 fail:0 skip:20 time:467s fi-kbl-r total:285 pass:258 dwarn:0 dfail:0 fail:0 skip:27 time:517s fi-pnv-d510 total:285 pass:219 dwarn:1 dfail:0 fail:0 skip:65 time:657s fi-skl-6260u total:285 pass:265 dwarn:0 dfail:0 fail:0 skip:20 time:442s fi-skl-6600u total:285 pass:258 dwarn:0 dfail:0 fail:0 skip:27 time:530s fi-skl-6700k2 total:285 pass:261 dwarn:0 dfail:0 fail:0 skip:24 time:502s fi-skl-6770hq total:285 pass:265 dwarn:0 dfail:0 fail:0 skip:20 time:493s fi-skl-guc total:285 pass:257 dwarn:0 dfail:0 fail:0 skip:28 time:431s fi-skl-gvtdvm total:285 pass:262 dwarn:0 dfail:0 fail:0 skip:23 time:444s fi-snb-2520m total:285 pass:245 dwarn:0 dfail:0 fail:0 skip:40 time:597s fi-snb-2600 total:285 pass:245 dwarn:0 dfail:0 fail:0 skip:40 time:408s Blacklisted hosts: fi-cnl-psr total:224 pass:198 dwarn:0 dfail:0 fail:1 skip:24 fi-glk-j4005 total:285 pass:256 dwarn:0 dfail:0 fail:0 skip:29 time:485s
8eb8f6d91a7eb7aa94aae5d7f29d985860385be9 drm-tip: 2018y-03m-27d-09h-31m-26s UTC integration manifest d628d88d98af i915.rst: narration for batchbuffer submission + links to source code doc entries on the subject b109dc25d336 i915: add doc for synchronization1b773741439b i915: add documentation for a bit on batchbuffer submission backend 0a02bba1c32d i915: add documentation of what happens at the bottom of submitting a batchbuffer 263e2bc9cb2f i915.rst: Narration overview on GEM + minor reorder to improve narration
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8499/issues.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.IGT: failure for Documentation patch for batchbuffer submission (rev3)
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Documentation patch for batchbuffer submission (rev3)
URL : https://patchwork.freedesktop.org/series/38433/
State : failure
== Summary ==
---- Possible new issues:
Test kms_frontbuffer_tracking:
Subgroup fbc-1p-primscrn-spr-indfb-draw-mmap-wc:
pass -> FAIL (shard-apl)---- Known issues:
Test drv_selftest:
Subgroup live_gtt:
pass -> INCOMPLETE (shard-apl) fdo#103927
Test kms_flip:
Subgroup 2x-flip-vs-expired-vblank-interruptible:
pass -> FAIL (shard-hsw) fdo#102887
Subgroup 2x-flip-vs-wf_vblank-interruptible:
fail -> PASS (shard-hsw) fdo#100368 +2
Subgroup dpms-vs-vblank-race:
pass -> FAIL (shard-apl) fdo#103060fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
fdo#102887 https://bugs.freedesktop.org/show_bug.cgi?id=102887
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#103060 https://bugs.freedesktop.org/show_bug.cgi?id=103060
shard-apl total:3473 pass:1806 dwarn:1 dfail:0 fail:9 skip:1655 time:12404s shard-hsw total:3495 pass:1780 dwarn:1 dfail:0 fail:4 skip:1709 time:11507s shard-snb total:3495 pass:1374 dwarn:1 dfail:0 fail:3 skip:2117 time:6994s
Blacklisted hosts:
shard-kbl total:3495 pass:1956 dwarn:1 dfail:0 fail:9 skip:1529 time:9707s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8499/shards.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx