From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Hellstrom Subject: Re: Unmappable VRAM patchset V4 Date: Mon, 01 Mar 2010 13:03:38 +0100 Message-ID: <4B8BAD1A.7020600@vmware.com> References: <1267117309-1266-1-git-send-email-jglisse@redhat.com> <21d7e9971002282144w59b0a235q75615c9fedf72af6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21d7e9971002282144w59b0a235q75615c9fedf72af6@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.sourceforge.net To: Dave Airlie Cc: Jerome Glisse , "skeggsb@gmail.com" , "dri-devel@lists.sf.net" List-Id: dri-devel@lists.freedesktop.org Dave Airlie wrote: > On Fri, Feb 26, 2010 at 3:01 AM, Jerome Glisse wrote: > >> Updated patchset, to apply cleanly on top of TTM split no_wait argument. >> Compile tested for nouveau+vmwgfx, test in progress for radeon. >> >> So with the new change radeon won't wait for bo reserving other bo >> in fault path but will wait the GPU (hoping it doesn't lockup ;)) >> This should address concern about the wait/locking issue. >> > > Thomas any time for this yet? I'd like to pull this in obviously, but > it would be nice to know if Jerome has addressed all concerns. > > Dave. > Hi Dave! My schedule is currently a bit tight. I think the immediate deadlock concerns are met, but I'd to take a deeper look at some things that look a bit suspicious, but I think the overall approach is ok. I'll hopefully be able to do a review on wednesday. /Thomas ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev --