On Thu, Aug 15, 2013 at 12:13 PM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > I've just pushed a (cairo-based!) tool to intel-gpu-tools, > intel_framebuffer_dump, that should also confirm everything we've found > so far - i.e. that we read and write consistently through the GTT into > stolen memory. Which just leaves the step between memory and the > display. Thanks. This still forces me to upgrade to a higher cairo version, not sure which to which more depends this will lead. So, the root-cause for my issue is not intel-gfx related? BIOS? Quirk needed? Other areas? ( I have seen some mm/soft-dirty fixes in mainline... Is CONFIG_MEM_SOFT_DIRTY=y an option to play with? Or how to interpret this snooped/LLC dirty outputs I had sent? ) - Sedat - P.S.: Commits in recent mainline: mm: save soft-dirty bits on file pages mm: save soft-dirty bits on swapped pages _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
