On Mon, Nov 07, 2016 at 10:26:59PM +0000, Robert Bragg wrote: > The command parser no longer whitelists or does anything special for the > OACONTROL register which is now considered owned by i915-perf. > > As a follow up the plan is to at least check that attempting to write to > OACONTROL from userspace must not fail with an EINVAL error, otherwise > Mesa's graceful fallback path for not being able to write to OACONTROL > via LRI commands will cause Mesa applications to abort(). This was part of the earlier ABI, and will remain ABI for those kernels. If the cmdparser advertises that it expects OACONTROL to be paired, we should keep testing that the cmdparser does as advertised. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
