Re: [Intel-gfx] [PATCH igt 2/2] igt/kms_frontbuffer_tracking: Access via GGTT is not guaranteed to be tracked

2017-12-19 Thread Arkadiusz Hiler
On Thu, Dec 14, 2017 at 08:09:21PM +, Chris Wilson wrote: > Quoting Chris Wilson (2017-12-07 09:41:26) > > As the system may use a partial vma for a GGTT mmap, access via the GGTT > > mmap is not guaranteed to be tracked by FBC's fence. The rule expressed has > > been that any access to the fro

Re: [Intel-gfx] [PATCH igt 2/2] igt/kms_frontbuffer_tracking: Access via GGTT is not guaranteed to be tracked

2017-12-14 Thread Chris Wilson
Quoting Chris Wilson (2017-12-07 09:41:26) > As the system may use a partial vma for a GGTT mmap, access via the GGTT > mmap is not guaranteed to be tracked by FBC's fence. The rule expressed has > been that any access to the frontbuffer should be followed by a fb-dirty > ioctl, so always apply and

[Intel-gfx] [PATCH igt 2/2] igt/kms_frontbuffer_tracking: Access via GGTT is not guaranteed to be tracked

2017-12-07 Thread Chris Wilson
As the system may use a partial vma for a GGTT mmap, access via the GGTT mmap is not guaranteed to be tracked by FBC's fence. The rule expressed has been that any access to the frontbuffer should be followed by a fb-dirty ioctl, so always apply and expect the driver to ellide no-ops. Signed-off-by