From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maarten Lankhorst Subject: Re: [PATCH] drm/ttm: remove EBUSY handling in ttm_execbuf_util Date: Mon, 20 Aug 2012 19:55:25 +0200 Message-ID: <50327A0D.7080805@canonical.com> References: <50323EAC.5060107@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by gabe.freedesktop.org (Postfix) with ESMTP id D830C9E85D for ; Mon, 20 Aug 2012 10:55:26 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Jerome Glisse Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Hey, Op 20-08-12 17:15, Jerome Glisse schreef: > On Mon, Aug 20, 2012 at 9:42 AM, Maarten Lankhorst > wrote: >> How is this different from just calling with no_wait == false? >> As far as I can tell, both paths end up with the same result.. >> >> Signed-off-by: Maarten Lankhorst > NAK this seriously modify the behavior. The ttm_eu_del_from_lru_locked > part is important. It must happen with lru lock held and without any > dropping of this lock prior to wait for bo unreserve. > You're right, I missed the part where it removed those, causing the later patch to be wrong too. However I still think the code can be made more readable. Wouldn't it be better if it used the unlocked variants instead? It would save a lot of extra list traversals, and you could drop removed, reserved and put_count from ttm_validate_buffer. ~Maarten