From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Widawsky Subject: Re: [PATCH 5/5] drm/i915: Fix error capture on BYT/BDW Date: Sun, 26 Jan 2014 11:05:40 -0800 Message-ID: <20140126190540.GE894@bwidawsk.net> References: <1390616265-4329-1-git-send-email-benjamin.widawsky@intel.com> <1390616265-4329-5-git-send-email-benjamin.widawsky@intel.com> <20140126114740.GF23557@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.bwidawsk.net (bwidawsk.net [166.78.191.112]) by gabe.freedesktop.org (Postfix) with ESMTP id 2B90DFA44C for ; Sun, 26 Jan 2014 11:05:47 -0800 (PST) Content-Disposition: inline In-Reply-To: <20140126114740.GF23557@nuc-i3427.alporthouse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: Chris Wilson , Ben Widawsky , Intel GFX , Mika Kuoppala List-Id: intel-gfx@lists.freedesktop.org On Sun, Jan 26, 2014 at 11:47:40AM +0000, Chris Wilson wrote: > On Fri, Jan 24, 2014 at 06:17:45PM -0800, Ben Widawsky wrote: > > The previous check during error capture of whether or not the current VM > > should be scanned used, gen < 7. That was more or less trying to > > determine if there was a full PPGTT. At the time, this was sort of what > > I meant to do because I was more interested in working backwards from > > hardware state. However, this is incorrect because it will not include > > platforms that are greater than gen7, and not having PPGTT. Example > > would be BYT which is gen7 but doesn't have PPGTT, BDW, or any platform > > greater than gen7 with the PPGTT module parameter invoked. > > > > I am /assuming/ BYT was broken, I have not actually checked. > > > > While here, clean up the file a bit to avoid duplicate reads (now that > > the PPGTT info is in the error state). > > > > I think Mika/Chris may have been looking at this too. > > Sure, we are looking (for identifying the guilty request/batch) by using > the older, simpler mechanism of finding the first incomplete request. I > think that search is now definite since we preallocate the request and no > longer do request collascing if ENOMEM (i.e. there is a 1:1 relationship > between seqno/batch/request). > > That should also apply here and be much simpler. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre How does that solve hangs which aren't caused by requests? -- Ben Widawsky, Intel Open Source Technology Center