From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 07/13] drm/i915: Mark the cursor and the
	overlay as being part of the display planes
Date: Wed, 04 May 2011 20:47:45 +0100
Message-ID: <0d30dc$m412e6@orsmga001.jf.intel.com>
References: <1302771827-26112-1-git-send-email-chris@chris-wilson.co.uk>
	<1302771827-26112-8-git-send-email-chris@chris-wilson.co.uk>
	<yunvcxq4cke.fsf@aiko.keithp.com>
	<b7da2f$rbg1cb@fmsmga001.fm.intel.com>
	<yunr58e1ey5.fsf@aiko.keithp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
	by gabe.freedesktop.org (Postfix) with ESMTP id 992029E709
	for <intel-gfx@lists.freedesktop.org>;
	Wed,  4 May 2011 12:47:48 -0700 (PDT)
In-Reply-To: <yunr58e1ey5.fsf@aiko.keithp.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Keith Packard <keithp@keithp.com>, intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Wed, 04 May 2011 11:46:42 -0700, Keith Packard <keithp@keithp.com> wrote:
> On Wed, 04 May 2011 19:28:35 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > to simply mark the device as uninterruptible for the duration.
> > 
> > The code now does the latter.
> 
> I'm good with that plan during modesetting, the question is whether the
> new users of this function should allow for interrupts.

The callers control whether that function is interruptible or not by
setting a flag on the device. So far the only piece of code that we have
allowed to run non-interruptible is the modesetting.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre