On Wed, Apr 13, 2016 at 10:46 PM, Daniel Vetter <daniel@xxxxxxxx> wrote: > I fully agree that we can try to do a better job on documenting this > stuff, and maybe exposing more information through stable interfaces. > > But adding new abi to enable/disable stuff sounds like jumping into > the middle of the use-case story, ignoring everything else. And I > think that was roughly what we agreed at that meeting - we can add > knobs when it makes sense, but only when it makes sense. I'm still not > sold on the "debug by powertop" solution. Maybe over the top: Exposing a list of marketing features ( why are e.g. watermark levels not in there - it seems completely arbitrary) and then debug issues by randomly whacking those until insight hits you isn't systematic debugging. And I don't want to enshrine that kind of random whacking into ABI as the recommended way to debug i915.ko issues. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
