dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm: Aggressively disable vblanks
Date: Mon, 20 Dec 2010 22:55:46 -0500	[thread overview]
Message-ID: <AANLkTimk6RLkr8Lt76cR8ncLW_3kaX6Dqa+=id9_G-8C@mail.gmail.com> (raw)
In-Reply-To: <yunbp4frdmo.fsf@aiko.keithp.com>

On Mon, Dec 20, 2010 at 10:47 PM, Keith Packard <keithp@keithp.com> wrote:
> On Mon, 20 Dec 2010 22:34:12 -0500, Andrew Lutomirski <luto@mit.edu> wrote:
>
>> But five seconds is a *long* time, and anything short enough that the
>> interrupt actually gets turned off in normal use risks the same race.
>
> Right, so eliminating any race seems like the basic requirement. Can
> that be done?

I'll give it a shot.

Do you know if there's an existing tool to call drm_wait_vblank from
userspace for testing?  I know approximately nothing about libdrm or
any userspace graphics stuff whatsoever.

--Andy

>
> --
> keith.packard@intel.com
>

  reply	other threads:[~2010-12-21  3:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 19:00 [PATCH] drm: Aggressively disable vblanks Andy Lutomirski
2010-12-21  3:23 ` Keith Packard
2010-12-21  3:34   ` [Intel-gfx] " Andrew Lutomirski
2010-12-21  3:47     ` Keith Packard
2010-12-21  3:55       ` Andrew Lutomirski [this message]
2010-12-21  4:03         ` Jesse Barnes
     [not found] <mailman.28.1292917668.19577.dri-devel@lists.freedesktop.org>
2010-12-22  4:36 ` [Intel-gfx] " Mario Kleiner
2010-12-22 17:23   ` Jesse Barnes
2010-12-22 21:06     ` Mario Kleiner
2010-12-26 14:53       ` Andrew Lutomirski
2010-12-26 23:58         ` Mario Kleiner
2010-12-27 11:16           ` Ville Syrjälä
2010-12-27 21:30             ` Mario Kleiner
2011-01-10  2:24           ` Andrew Lutomirski

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='AANLkTimk6RLkr8Lt76cR8ncLW_3kaX6Dqa+=id9_G-8C@mail.gmail.com' \
    --to=luto@mit.edu \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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;
as well as URLs for NNTP newsgroup(s).