Fixes which failed clean cherry-pick to drm-intel-fixes

Fixes which failed clean cherry-pick to drm-intel-fixes

[Rodrigo Vivi]

Hi Chris,

4 of your fixes failed the clean cherry-pick of drm-intel-fixes.

b647c7df01b7 ("drm/i915: Fixup preempt-to-busy vs resubmission of a virtual request")
cb2377a919bb ("drm/i915: Fixup preempt-to-busy vs reset of a virtual request")
a4311745bba9 ("drm/i915/userptr: Never allow userptr into the mappable GGTT")
2935ed5339c4 ("drm/i915: Remove logical HW ID")

Is anyone of those critical?
If so, could you please provide a version for drm-intel-fixes?

Thanks,
Rodrigo.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: Fixes which failed clean cherry-pick to drm-intel-fixes

[Chris Wilson]

Quoting Rodrigo Vivi (2019-10-07 18:54:35)
> Hi Chris,
> 
> 4 of your fixes failed the clean cherry-pick of drm-intel-fixes.
> 
> b647c7df01b7 ("drm/i915: Fixup preempt-to-busy vs resubmission of a virtual request")
> cb2377a919bb ("drm/i915: Fixup preempt-to-busy vs reset of a virtual request")
> a4311745bba9 ("drm/i915/userptr: Never allow userptr into the mappable GGTT")
> 2935ed5339c4 ("drm/i915: Remove logical HW ID")
> 
> Is anyone of those critical?
> If so, could you please provide a version for drm-intel-fixes?

See https://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=dif

I've not bothered with 2935ed5339c4, that seems more hassle than I care
for atm. The risk is only if people adopt I915_CONTEXT_PARAM_SET_ENGINE
and use it in novel ways and still the HW may not notice. So we are
probably going to get the next kernel out before people notice any
breakage.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx