[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0C18FE92A7765D4EB9EE5D38D86A563A53A9C855@SHSMSX103.ccr.corp.intel.com>
Date: Mon, 26 Dec 2016 07:41:36 +0000
From: "Du, Changbin" <changbin.du@...el.com>
To: Chris Wilson <chris@...is-wilson.co.uk>
CC: "Vetter, Daniel" <daniel.vetter@...el.com>,
"airlied@...ux.ie" <airlied@...ux.ie>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: RE: [Intel-gfx] [PATCH] drm/i915: check if execlist_port is empty
before using its content
> On Fri, Dec 23, 2016 at 01:46:36PM +0800, changbin.du@...el.com wrote:
> > From: "Du, Changbin" <changbin.du@...el.com>
> >
> > This patch fix a crash in function reset_common_ring. In this case,
> > the port[0].request is null when reset the render ring, so a null
> > dereference exception is raised. We need to check execlist_port status
> > first.
>
> No. The root cause is whatever got you into the illegal condition in the
> first place.
> -Chris
>
Thanks, I will restudy the code after process my current job. Since this happen
on gvt guest, so this may related to gvt emulation.
> --
> Chris Wilson, Intel Open Source Technology Centre
Powered by blists - more mailing lists