Am 30.06.2017 um 08:51 schrieb Michel Dänzer:
We can deal with that internally in the kernel, while fixing the existing flag for userspace.
And as I said, NAK to that approach. I'm not going to add a CPU_ACCESS_REALLY_REQUIRED flag in the kernel just because mesa has messed up it's use case.
We could agree on filtering that flag from userspace when BOs are created and/or map it to a CREATE_CPU_ACCESS_HINT flag. But I would rather want to avoid that as well.
Christian. _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
