From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dan Aloni <alonid@gmail.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Suggestions on fixing fill_modes ioctl() delays under i915
Date: Mon, 16 Apr 2012 14:41:28 +0100 [thread overview]
Message-ID: <1334583703_7713@CP5-2952> (raw)
In-Reply-To: <CAAV7fNoXts83NmokYXPhpAjfxqgpoUVzcdVhFCSsMtn=Upq+ZQ@mail.gmail.com>
On Mon, 16 Apr 2012 15:04:50 +0300, Dan Aloni <alonid@gmail.com> wrote:
> Now you might ask why it is annoying. Well, for instance, say you are
> debugging an SDL application. Those type of applications usually result in
> the GET_CONTROLLERS ioctl() being called by the X server, and re-running
> the same application in a development cycle makes this issue
> quite noticeable.
The actual problem here is the application requesting a probe of all
outputs rather than the list of current outputs.
See RRGetScreenResourcesCurrent.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-04-16 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 12:04 Suggestions on fixing fill_modes ioctl() delays under i915 Dan Aloni
2012-04-16 13:33 ` Eugeni Dodonov
2012-04-16 15:54 ` Dan Aloni
2012-04-16 16:37 ` Adam Jackson
2012-04-16 16:53 ` Dan Aloni
2012-04-16 13:41 ` Chris Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1334583703_7713@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=alonid@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox