Re: [Intel-gfx] [PATCH 18/66] drm/i915: Always defer fenced work to the worker

On 7/31/20 3:28 PM, Chris Wilson wrote: Quoting Thomas Hellström (Intel) (2020-07-31 10:03:59) On 7/15/20 1:50 PM, Chris Wilson wrote: Currently, if an error is raised we always call the cleanup locally [and skip the main work callback]. However, some future users Could you add an example of

Re: [Intel-gfx] [PATCH 18/66] drm/i915: Always defer fenced work to the worker

Quoting Thomas Hellström (Intel) (2020-07-31 10:03:59) > > On 7/15/20 1:50 PM, Chris Wilson wrote: > > Currently, if an error is raised we always call the cleanup locally > > [and skip the main work callback]. However, some future users > Could you add an example of those future users? In the

Re: [Intel-gfx] [PATCH 18/66] drm/i915: Always defer fenced work to the worker

On 7/15/20 1:50 PM, Chris Wilson wrote: Currently, if an error is raised we always call the cleanup locally [and skip the main work callback]. However, some future users Could you add an example of those future users? may need to take a mutex to cleanup and so we cannot immediately execute

[Intel-gfx] [PATCH 18/66] drm/i915: Always defer fenced work to the worker

Currently, if an error is raised we always call the cleanup locally [and skip the main work callback]. However, some future users may need to take a mutex to cleanup and so we cannot immediately execute the cleanup as we may still be in interrupt context. With the execute-immediate flag, for most