Thank you @llandwerlin. It might be needed. I will study more carefully to avoid some performance drop.
Yes, kernel sets it to disabled in each context start. Currently, if it's enabled in this blorp condition, it will reply on next kernel context run. Agree with that we need to find a place to clear it after resolve path closed to minimize its enabled durations. We can verify more on the needed changes then put new MR for that.
Thanks for suggestion. Just updated the new patch-set accordingly.
zhenhanintel (c41ba692) at 01 Apr 07:52
Blorp: enable RCC RHWO optimization in resovle path
The disable is set in KMD. This patch is just make sure it is enabled in this particular case. Yes, another discussion is about move the change from KMD to UMD that needs your comments also.
In gen125, the configure place is moved to another register of 3DSTATE_3D_MODE
. This patch does not include the changes for gen125.