Messages in this thread | | | Date | Thu, 23 Feb 2012 17:31:24 +0000 | Subject | Re: responsiveness: newer kernels causing lagging and blocking | From | Dave Airlie <> |
| |
On Thu, Feb 23, 2012 at 5:29 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > On Thu, Feb 23, 2012 at 9:21 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote: >> >> One mystery that has never been resolved is just why wine causes a flood >> of xrandr/connection probes, and then there is still the underlying issue >> that probing blocks the device and causes noticeable latency. > > Is there any chance that the EDID code would just have a "if I probed > in the last second or two, let's not do it again and instead just > return the cached data from last time" thing to just protect against > some odd interrupt flood (or a user that asks for edid information > explicitly like xrandr).
X already does that, if you can the randr interfaces it doesn't cause a probe unless you ask for it.
wine must be doing something silly or just needs to call a different interface.
Dave. > > Linus > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |