messages from 2023-05-22 11:09:13 to 2023-05-24 12:37:28 UTC [more...]
[Intel-xe] [RFC PATCH 0/2] Implement vma madvise ioctl
2023-05-24 12:36 UTC (3+ messages)
` [Intel-xe] [RFC PATCH 1/2] drm/xe: Expose vma bind-unbind functions
` [Intel-xe] [RFC PATCH 2/2] drm/xe: Implement madvise ioctl for vma
[Intel-xe] [PATCH v4] drm/xe/pm: Disable PM on unbounded pcie parent bridge
2023-05-24 9:45 UTC (5+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/pm: Disable PM on unbounded pcie parent bridge (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH 1/2] drm/xe: Fix uninitialized variables
2023-05-24 9:04 UTC (9+ messages)
` [Intel-xe] [PATCH 2/2] drm/xe: Fix check for platform without geometry pipeline
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Fix uninitialized variables
` [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-24 8:16 UTC (5+ messages)
[Intel-xe] [PATCH v2 1/1] drm/xe: Add a debugfs for faking gt reset failure
2023-05-24 7:40 UTC (5+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v2,1/1] "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH] drm/xe: Add stepping support for GMD_ID platforms
2023-05-24 7:07 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] [RFC 1/1] drm/xe: Add a debugfs for faking gt reset failure
2023-05-24 6:18 UTC (3+ messages)
[Intel-xe] [PATCH] drm/xe: add a new sysfs directory for gtidle properties
2023-05-24 6:05 UTC (4+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: add a new sysfs directory for gtidle properties (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
[Intel-xe] [PATCH v2 0/8] Scheduler changes for upstreaming
2023-05-24 5:01 UTC (17+ messages)
` [Intel-xe] [PATCH v2 1/8] fixup! drm/sched: Convert drm scheduler to use a work queue rather than kthread
` [Intel-xe] [PATCH v2 2/8] drm/sched: Move schedule policy to scheduler
` [Intel-xe] [PATCH v2 3/8] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
` [Intel-xe] [PATCH v2 4/8] drm/xe: Use DRM_SCHED_POLICY_SINGLE_ENTITY mode
` [Intel-xe] [PATCH v2 5/8] drm/xe: Long running job update
` [Intel-xe] [PATCH v2 6/8] drm/xe: Ensure LR engines are not persistent
` [Intel-xe] [PATCH v2 7/8] drm/xe: Only try to lock external BOs in VM bind
` [Intel-xe] [PATCH v2 8/8] drm/xe: VM LRU bulk move
` [Intel-xe] ✓ CI.Patch_applied: success for Scheduler changes for upstreaming (rev3)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH 0/2] Update Xe uAPI in a minimally invasive way
2023-05-24 4:08 UTC (7+ messages)
` [Intel-xe] [PATCH 1/2] drm/xe: Add explicit padding to uAPI definition
` [Intel-xe] [PATCH 2/2] drm/xe: Validate uAPI padding and reserved fields
` [Intel-xe] ✓ CI.Patch_applied: success for Update Xe uAPI in a minimally invasive way
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH 1/2] xe/rpls: Add RPLS Support
2023-05-23 23:53 UTC (6+ messages)
` [Intel-xe] [PATCH 2/2] xe/rpls: Add Stepping info for RPLS
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] xe/rpls: Add RPLS Support
` [Intel-xe] ✗ CI.KUnit: failure "
[Intel-xe] [RFC] drm/xe: A minimal assert for some forcewake domain on xe_mmio
2023-05-23 23:52 UTC (8+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for "
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
[Intel-xe] [PATCH] drm/xe: Do not unbind destroyed vmas
2023-05-23 23:30 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 v2 0/6] i915: Move display identification/probing under display/
2023-05-23 14:43 UTC (19+ messages)
` [Intel-xe] [PATCH v2 1/6] drm/i915/display: Move display device info to header "
` [Intel-xe] [PATCH v2 2/6] drm/i915: Convert INTEL_INFO()->display to a pointer
` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH v2 3/6] drm/i915/display: Move display runtime info to display structure
` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH v2 4/6] drm/i915/display: Make display responsible for probing its own IP
` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH v2 5/6] drm/i915/display: Handle GMD_ID identification in display code
` [Intel-xe] [Intel-gfx] "
` [Intel-xe] [PATCH v2 6/6] drm/i915/display: Move feature test macros to intel_display_device.h
` [Intel-xe] [Intel-gfx] "
` [Intel-xe] ✗ CI.Patch_applied: failure for i915: Move display identification/probing under display/ (rev2)
[Intel-xe] [PATCH v9 1/8] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
2023-05-23 13:13 UTC (16+ messages)
` [Intel-xe] [PATCH v9 2/8] drm/xe: don't allocate under ct->lock
` [Intel-xe] [PATCH v9 3/8] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [PATCH v9 4/8] drm/xe: tweak lock ordering for freq_lock
` [Intel-xe] [PATCH v9 5/8] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [PATCH v9 6/8] drm/xe/ct: drop mem_access_get from g2h_worker_func()
` [Intel-xe] [PATCH v9 7/8] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [PATCH v9 8/8] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v9,1/8] 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] [PATCH] fixup! drm/xe/display: Implement display support
2023-05-23 12:24 UTC (8+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for fixup! drm/xe/display: Implement display support (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [RFC PATCH] drm/xe: add a new sysfs directory for gtidle properties
2023-05-23 7:13 UTC (3+ messages)
[Intel-xe] [PATCH] drm/doc/rfc/xe: No STAGING in drm
2023-05-23 6:40 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 0/8] Scheduler changes for upstreaming
2023-05-23 5:49 UTC (6+ messages)
` [Intel-xe] [PATCH 1/8] fixup! drm/sched: Convert drm scheduler to use a work queue rather than kthread
` [Intel-xe] [PATCH 3/8] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
[Intel-xe] [PATCH v2 0/8] Scheduler changes for upstreaming
2023-05-23 4:36 UTC (13+ messages)
` [Intel-xe] [PATCH v2 1/8] fixup! drm/sched: Convert drm scheduler to use a work queue rather than kthread
` [Intel-xe] [PATCH v2 2/8] drm/sched: Move schedule policy to scheduler
` [Intel-xe] [PATCH v2 3/8] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
` [Intel-xe] [PATCH v2 4/8] drm/xe: Use DRM_SCHED_POLICY_SINGLE_ENTITY mode
` [Intel-xe] [PATCH v2 5/8] drm/xe: Long running job update
` [Intel-xe] [PATCH v2 6/8] drm/xe: Ensure LR engines are not persistent
` [Intel-xe] [PATCH v2 7/8] drm/xe: Only try to lock external BOs in VM bind
` [Intel-xe] [PATCH v2 8/8] drm/xe: VM LRU bulk move
` [Intel-xe] ✓ CI.Patch_applied: success for Scheduler changes for upstreaming (rev2)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH 0/2] drm/xe: Proper cleanup in xe_device_create()
2023-05-22 20:46 UTC (6+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Proper cleanup in xe_device_create() (rev3)
` [Intel-xe] ✓ CI.KUnit: "
` [Intel-xe] ✓ CI.Build: "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH] drm/xe: Do not forget to drm_dev_put() in xe_pci_probe():
2023-05-22 20:28 UTC (7+ messages)
` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Do not forget to drm_dev_put() in xe_pci_probe(): (rev2)
` [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-22 19:10 UTC (7+ messages)
` [Intel-xe] [PATCH 3/5] drm/i915/display: Move display runtime info to display structure
` [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] [PATCH v3] drm/xe/pm: Disable PM on unbounded pcie parent bridge
2023-05-22 18:34 UTC (6+ messages)
[Intel-xe] [PATCH v8 1/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
2023-05-22 18:06 UTC (11+ messages)
` [Intel-xe] [PATCH v8 2/7] drm/xe: don't allocate under ct->lock
` [Intel-xe] [PATCH v8 3/7] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [PATCH v8 4/7] drm/xe: tweak lock ordering for freq_lock
` [Intel-xe] [PATCH v8 5/7] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [PATCH v8 6/7] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [PATCH v8 7/7] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v8,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] [PATCH v7 1/7] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
2023-05-22 16:47 UTC (11+ messages)
` [Intel-xe] [PATCH v7 2/7] drm/xe: don't allocate under ct->lock
` [Intel-xe] [PATCH v7 3/7] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [PATCH v7 4/7] drm/xe/ct: tweak lock ordering for freq_lock
` [Intel-xe] [PATCH v7 5/7] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [PATCH v7 6/7] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [PATCH v7 7/7] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v7,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] [PATCH v6 1/6] Revert "drm/xe: Use atomic instead of mutex for xe_device_mem_access_ongoing"
2023-05-22 15:13 UTC (11+ messages)
` [Intel-xe] [PATCH v6 2/6] drm/xe: don't allocate under ct->lock
` [Intel-xe] [PATCH v6 3/6] drm/xe: keep pulling mem_access_get further back
` [Intel-xe] [PATCH v6 4/6] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM
` [Intel-xe] [PATCH v6 5/6] drm/xe: fix xe_device_mem_access_get() races
` [Intel-xe] [PATCH v6 6/6] drm/xe: Use atomic for mem_access.ref
` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v6,1/6] 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] [PATCH] drm/xe: fix kernel-doc issues
2023-05-22 14:07 UTC (6+ messages)
` [Intel-xe] ✓ CI.Build: success for "
` [Intel-xe] ○ CI.BAT: info "
[Intel-xe] [PATCH v2 00/30] Separate GT and tile
2023-05-22 11:47 UTC (5+ messages)
` [Intel-xe] [PATCH v2 14/30] drm/xe: Clarify 'gt' retrieval for primary tile
` [Intel-xe] [PATCH v2 26/30] drm/xe/tlb: Obtain forcewake when doing GGTT TLB invalidations
[Intel-xe] [PATCH v2] drm: fix drmm_mutex_init()
2023-05-22 11:12 UTC (4+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox