From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 02/15] drm/i915: Don't emit mbox updates
 without semaphores
Date: Tue, 17 Dec 2013 22:47:30 +0000
Message-ID: <20131217224730.GC27858@nuc-i3427.alporthouse.com>
References: <1387255851-24824-1-git-send-email-benjamin.widawsky@intel.com>
	<1387255851-24824-3-git-send-email-benjamin.widawsky@intel.com>
	<20131217192441.GU22448@nuc-i3427.alporthouse.com>
	<20131217220223.GA10071@bwidawsk.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from fireflyinternet.com (mail.fireflyinternet.com [87.106.93.118])
	by gabe.freedesktop.org (Postfix) with ESMTP id 44605105B62
	for <intel-gfx@lists.freedesktop.org>;
	Tue, 17 Dec 2013 14:47:34 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <20131217220223.GA10071@bwidawsk.net>
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@lists.freedesktop.org
Errors-To: intel-gfx-bounces@lists.freedesktop.org
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>, Ben Widawsky <benjamin.widawsky@intel.com>
List-Id: intel-gfx@lists.freedesktop.org

On Tue, Dec 17, 2013 at 02:02:23PM -0800, Ben Widawsky wrote:
> On Tue, Dec 17, 2013 at 07:24:41PM +0000, Chris Wilson wrote:
> > On Mon, Dec 16, 2013 at 08:50:38PM -0800, Ben Widawsky wrote:
> > > Aside from the fact that it leaves confusing dumps on error capture, it
> > > is entirely unnecessary, and potentially harmful in cases like BDW,
> > > where the instruction has changed.
> > > 
> > > In reality (seemingly), this will have no behavioral impact.
> > > 
> > > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > 
> > The reason why we currently do is because i915.semaphores can change at
> > runtime. So we emit the instructions whilst i915.semaphores=0 just in
> > case, it is enabled later. This restriction can be lifted with a little
> > more work in handling the missed semaphores, I think, or it may just
> > require a proof that everything is safe as is.
> > -Chris
> > 
> 
> 
> It should still check the module parameter - I guess it would be nice to
> guard changing the module parameter with struct_mutex (generally, not
> just here), as that also breaks the emit path.
> 
> So in short, I think it's broken for two reasons.
> 
> My (and Daniel's) vote is to just make the module param static.

Dynamic i915.semaphores is something I can live happily without. If we
ever do need such a thing, it needs to be internal to the kernel.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre