dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ilija Hadzic <ihadzic@research.bell-labs.com>
Cc: "Michel Dänzer" <michel@daenzer.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm: do not sleep on vblank while holding a mutex
Date: Fri, 28 Oct 2011 16:51:49 +0200	[thread overview]
Message-ID: <20111028145149.GC2919@phenom.ffwll.local> (raw)
In-Reply-To: <Pine.GSO.4.62.1110280703400.16410@umail>

On Fri, Oct 28, 2011 at 07:10:51AM -0500, Ilija Hadzic wrote:
> I'll keep it then and figure out the best mutex/spinlock to use. It
> can be anything that exists on one-per-CRTC basis (vblank waits on
> different CTCs are not contending). The critical section is from
> that switch in which vblwait->request.sequence is incremented until
> it is assigned to dev->last_vblank_wait[crtc] (and we are only
> protecting that section against itself, executed in contexts of
> different PIDs).
> 
> I guess we settled now on this patch (other comments will be
> addressed in a different set of patches).

If you settle on keeping ->last_vblank_wait I think the easiest is to wrap
it with the dev->vbl_lock spinlock everywhere.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2011-10-28 14:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26  2:20 drm: fix one flawed mutex grab and remove some spurious mutex grabs Ilija Hadzic
2011-10-26  2:20 ` [PATCH 1/3] drm: no need to hold global mutex for static data Ilija Hadzic
2011-10-26  7:44   ` Daniel Vetter
2011-10-26  2:20 ` [PATCH 2/3] drm: make DRM_UNLOCKED ioctls with their own mutex Ilija Hadzic
2011-10-26  7:47   ` Daniel Vetter
2011-10-26 16:11     ` Ilija Hadzic
2011-10-26 20:01       ` Daniel Vetter
2011-10-26  2:20 ` [PATCH 3/3] drm: do not sleep on vblank while holding a mutex Ilija Hadzic
2011-10-26  7:54   ` Daniel Vetter
2011-10-26 22:33     ` Ilija Hadzic
2011-10-27 10:43       ` Daniel Vetter
2011-10-27 14:10         ` Alan Coopersmith
2011-10-27 14:20           ` Ilija Hadzic
2011-10-28  3:19         ` Ilija Hadzic
2011-10-28  4:36           ` Ilija Hadzic
2011-10-28  6:59           ` Michel Dänzer
2011-10-28  9:20             ` Daniel Vetter
2011-10-28 12:10               ` Ilija Hadzic
2011-10-28 14:51                 ` Daniel Vetter [this message]
2011-10-28  9:30           ` Daniel Vetter
2011-10-26  8:02   ` Michel Dänzer
2011-10-26 22:50     ` Ilija Hadzic
     [not found] <mailman.37.1319803862.23620.dri-devel@lists.freedesktop.org>
2011-10-28 18:15 ` Mario Kleiner
2011-10-28 19:15   ` Daniel Vetter
2011-10-28 19:53     ` Mario Kleiner

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=20111028145149.GC2919@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ihadzic@research.bell-labs.com \
    --cc=michel@daenzer.net \
    /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