mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2025-01-06 05:06:29 +00:00
a85607e3cf
No DRM scheduler changes required, drivers just return NULL in run_job vfunc. The rough consensus is that no helper or extra scaffolding is needed around long-running jobs and no further changes to drm-scheduler. At least for now. Other drivers that currently do long-running workloads have no plat to use drm-scheduler. Besides, the current consensus is that this solution of simply returning NULL to the run_job function should work without extra code duplication or complication. On top of that, this item was already a non-blocking one for upstreaming Xe, so let's move that to the 'Completed' section and revisit the long-running solution as a community after Xe is integrated in DRM. Signed-off-by: Matthew Brost <matthew.brost@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20231201042158.80009-2-rodrigo.vivi@intel.com Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> |
||
---|---|---|
.. | ||
amdgpu | ||
bridge | ||
dp-mst | ||
imagination | ||
rfc | ||
afbc.rst | ||
automated_testing.rst | ||
backlight.rst | ||
driver-uapi.rst | ||
drivers.rst | ||
drm-client.rst | ||
drm-internals.rst | ||
drm-kms-helpers.rst | ||
drm-kms.rst | ||
drm-mm.rst | ||
drm-uapi.rst | ||
drm-usage-stats.rst | ||
drm-vm-bind-async.rst | ||
drm-vm-bind-locking.rst | ||
i915.rst | ||
implementation_guidelines.rst | ||
index.rst | ||
introduction.rst | ||
kms-properties.csv | ||
komeda-kms.rst | ||
mcde.rst | ||
meson.rst | ||
msm-crash-dump.rst | ||
panfrost.rst | ||
pl111.rst | ||
tegra.rst | ||
todo.rst | ||
tve200.rst | ||
v3d.rst | ||
vc4.rst | ||
vga-switcheroo.rst | ||
vgaarbiter.rst | ||
vkms.rst | ||
xen-front.rst |