Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
 messages from 2023-05-16 14:47:51 to 2023-05-18 21:15:01 UTC [more...]

[Intel-xe] [PATCH v4 01/11] drm/xe: Introduce the dev_coredump infrastructure
 2023-05-18 21:14 UTC  (22+ messages)
` [Intel-xe] [PATCH v4 02/11] drm/xe: Do not take any action if our device was removed
` [Intel-xe] [PATCH v4 03/11] drm/xe: Extract non mapped regions out of GuC CTB into its own struct
` [Intel-xe] [PATCH v4 04/11] drm/xe: Convert GuC CT print to snapshot capture and print
` [Intel-xe] [PATCH v4 05/11] drm/xe: Add GuC CT snapshot to xe_devcoredump
` [Intel-xe] [PATCH v4 06/11] drm/xe: Introduce guc_submit_types.h with relevant structs
` [Intel-xe] [PATCH v4 07/11] drm/xe: Convert GuC Engine print to snapshot capture and print
` [Intel-xe] [PATCH v4 08/11] drm/xe: Add GuC Submit Engine snapshot to xe_devcoredump
` [Intel-xe] [PATCH v4 09/11] drm/xe: Convert Xe HW Engine print to snapshot capture and print
` [Intel-xe] [PATCH v4 10/11] drm/xe: Add HW Engine snapshot to xe_devcoredump
` [Intel-xe] [PATCH v4 11/11] drm/xe: Limit CONFIG_DRM_XE_SIMPLE_ERROR_CAPTURE to itself
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v4,01/11] drm/xe: Introduce the dev_coredump infrastructure
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
  ` [Intel-xe] [PATCH] drm/xe: Introduce the dev_coredump infrastructure. 65; 7002; 1c The goal is to use devcoredump infrastructure to report error states captured at the crash time
` [Intel-xe] ✗ CI.Patch_applied: failure for series starting with drm/xe: Introduce the dev_coredump infrastructure. 65; 7002; 1c The goal is to use devcoredump infrastructure to report error states captured at the crash time. (rev2)

[Intel-xe] [PATCH] drm/xe: Fail xe_device_create() if wq allocation fails
 2023-05-18 20:52 UTC  (6+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH 00/26] Separate GT and tile
 2023-05-18 19:54 UTC  (36+ messages)
` [Intel-xe] [PATCH 02/26] drm/xe: Introduce xe_tile
` [Intel-xe] [PATCH 06/26] drm/xe: Move VRAM from GT to tile
` [Intel-xe] [PATCH 07/26] drm/xe: Memory allocations are tile-based, not GT-based
` [Intel-xe] [PATCH 08/26] drm/xe: Move migration from GT to tile
` [Intel-xe] [PATCH 09/26] drm/xe: Clarify 'gt' retrieval for primary tile
` [Intel-xe] [PATCH 10/26] drm/xe: Drop vram_id
` [Intel-xe] [PATCH 11/26] drm/xe: Drop extra_gts[] declarations and XE_GT_TYPE_REMOTE
` [Intel-xe] [PATCH 12/26] drm/xe: Allocate GT dynamically
` [Intel-xe] [PATCH 13/26] drm/xe: Add media GT to tile
` [Intel-xe] [PATCH 14/26] drm/xe: Move display IRQ postinstall out of GT function
` [Intel-xe] [PATCH 15/26] drm/xe: Interrupts are delivered per-tile, not per-GT
` [Intel-xe] [PATCH 16/26] drm/xe/irq: Handle ASLE backlight interrupts at same time as display
` [Intel-xe] [PATCH 17/26] drm/xe/irq: Actually call xe_irq_postinstall()
` [Intel-xe] [PATCH 19/26] drm/xe/irq: Untangle postinstall functions
` [Intel-xe] [PATCH 20/26] drm/xe: Replace xe_gt_irq_postinstall with xe_irq_enable_hwe
` [Intel-xe] [PATCH 26/26] drm/xe: Clarify source of GT log messages

[Intel-xe] [PATCH 0/4] Revert frontbuffer tracking removal
 2023-05-18 19:52 UTC  (2+ messages)

[Intel-xe] [PATCH] drm/xe: Allow scanout of bos that can be migrated to lmem
 2023-05-18 18:44 UTC  (9+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH v4 1/2] drm/xe: Introduce GT oriented log messages
 2023-05-18 18:05 UTC  (8+ messages)
` [Intel-xe] [PATCH v4 2/2] drm/xe: Use GT oriented log messages in xe_gt.c
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v4,1/2] drm/xe: Introduce GT oriented log messages
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH v3] drm/xe/pm: Disable PM on unbounded pcie parent bridge
 2023-05-18 17:11 UTC  (6+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH v6 0/4] drm/xe: Rework multi tile device memory initialization
 2023-05-18 11:40 UTC  (11+ messages)
` [Intel-xe] [PATCH 1/4] drm/xe: Rework size helper to be a little more correct
` [Intel-xe] [PATCH 2/4] drm/xe: Simplify rebar sizing
` [Intel-xe] [PATCH 3/4] drm/xe: Size GT device memory correctly
` [Intel-xe] [PATCH 4/4] drm/xe: Rename GPU offset helper to reflect true usage
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Rework multi tile device memory initialization (rev6)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH 0/5] i915: Move display identification/probing under display/
 2023-05-18 10:44 UTC  (16+ messages)
` [Intel-xe] [PATCH 1/5] drm/i915/display: Move display device info to header "
  ` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH 2/5] drm/i915: Convert INTEL_INFO()->display to a pointer
  ` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH 3/5] drm/i915/display: Move display runtime info to display structure
  ` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH 4/5] drm/i915/display: Make display responsible for probing its own IP
  ` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH 5/5] drm/i915/display: Handle GMD_ID identification in display code
  ` [Intel-xe] [Intel-gfx] "
` [Intel-xe] ✗ CI.Patch_applied: failure for i915: Move display identification/probing under display/

[Intel-xe] [PATCH v5 1/7] drm: fix drmm_mutex_init()
 2023-05-18 10:16 UTC  (26+ messages)
` [Intel-xe] [PATCH v5 2/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
` [Intel-xe] [PATCH v5 3/7] drm/xe: don't allocate under ct->lock
` [Intel-xe] [PATCH v5 4/7] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [PATCH v5 5/7] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [PATCH v5 6/7] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [PATCH v5 7/7] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v5,1/7] drm: fix drmm_mutex_init()
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v5,1/7] drm: fix drmm_mutex_init() (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH] drm/xe: Apply upper limit to sg element size
 2023-05-18  5:32 UTC  (7+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH v3 1/2] drm/xe: Introduce GT oriented log messages
 2023-05-17 23:09 UTC  (4+ messages)
` [Intel-xe] [PATCH v3 2/2] drm/xe: Use GT oriented log messages in xe_gt.c

[Intel-xe] [PATCH v3 0/9] Dump + OOB workarounds
 2023-05-17 22:43 UTC  (28+ messages)
` [Intel-xe] [PATCH v3 1/9] drm/xe: Fix Wa_22011802037 annotation
` [Intel-xe] [PATCH v3 2/9] drm/xe/rtp: Split rtp process initialization
` [Intel-xe] [PATCH v3 3/9] drm/xe/rtp: Add "_sr" to entry/function names
` [Intel-xe] [PATCH v3 4/9] drm/xe/rtp: Allow to track active workarounds
` [Intel-xe] [PATCH v3 5/9] drm/xe/wa: Track gt/engine/lrc "
` [Intel-xe] [PATCH v3 6/9] drm/xe/debugfs: Dump "
` [Intel-xe] [PATCH v3 7/9] drm/xe/rtp: Add support for entries with no action
` [Intel-xe] [PATCH v3 8/9] drm/xe: Add support for OOB workarounds
` [Intel-xe] [PATCH v3 9/9] drm/xe/guc: Port workarounds to OOB infra
` [Intel-xe] ✓ CI.Patch_applied: success for Dump + OOB workarounds
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "

[Intel-xe] [PATCH v2 00/31] Upstreaming prep / all of mbrosts patches
 2023-05-17 16:53 UTC  (3+ messages)
` [Intel-xe] [PATCH v2 30/31] drm/xe: remove async worker, sync binds, new error handling

[Intel-xe] [PATCH 0/2] Conform to dma-fence rules
 2023-05-17 14:55 UTC  (7+ messages)
` [Intel-xe] [PATCH 1/2] drm/xe: Allow compute VMs to output dma-fences on binds
` [Intel-xe] [PATCH 2/2] drm/xe: Allow dma-fences as in-syncs for compute / faulting VM
` [Intel-xe] ✓ CI.Patch_applied: success for Conform to dma-fence rules
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH v5 0/4] drm/xe: Rework multi tile device memory initialization
 2023-05-17 14:03 UTC  (4+ messages)
` [Intel-xe] [PATCH 2/4] drm/xe: Simplify rebar sizing

[Intel-xe] [PATCH v2] drm/xe/pm: WARN_ON() on unbounded pcie parent bridge device
 2023-05-17 12:57 UTC  (3+ messages)

[Intel-xe] [CI 1/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
 2023-05-17 12:43 UTC  (15+ messages)
` [Intel-xe] [CI 2/7] drm/xe: don't allocate under ct->lock
` [Intel-xe] [CI 3/7] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [CI 4/7] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [CI 5/7] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [CI 6/7] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] [CI 7/7] HAX
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,1/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,1/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing" (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "

[Intel-xe] [PATCH 0/4] drm/xe: use hotplug irq code from i915
 2023-05-17  8:04 UTC  (4+ messages)
` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support

[Intel-xe] [PATCH] fixup! drm/i915/display: Remaining changes to make xe compile
 2023-05-17  7:53 UTC  (3+ messages)

[Intel-xe] [PATCH v2 0/2] drm/xe: Call exit functions when xe_register_pci_driver() fails
 2023-05-16 20:53 UTC  (5+ messages)
` [Intel-xe] ○ CI.BAT: info for drm/xe: Call exit functions when xe_register_pci_driver() fails (rev2)

[Intel-xe] [PATCH v2 1/1] drm/xe: Notify Userspace when engine/gt reset fails
 2023-05-16 17:57 UTC  (7+ messages)

[Intel-xe] [PATCH v3 0/2] drm/xe: Fix unprotected rebind_list accesses
 2023-05-16 15:13 UTC  (7+ messages)
` [Intel-xe] [PATCH v3 1/2] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs
` [Intel-xe] [PATCH v3 2/2] "
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Fix unprotected rebind_list accesses
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox