From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF8A54C66; Tue, 17 Sep 2024 13:47:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726580835; cv=none; b=UkmM+/Kkodq5MCWlFXwjhhDCLtdpAX0zf5bLXjLRTmVSnccLc/p7EaOksJD+hnXwGUeu8C+D0i6Lra72QNDjf8w5vyHyKUrgEr8IyqX4VO0QS/3IhS/eYU1pkKXhRd73Diqk01G09OahatKXIkVZ7yiRMGRWVtvL+DmLK0fLb98= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726580835; c=relaxed/simple; bh=7y6lHUpzj4ENEmnHvaebsCoZS+iyBAZnVBKU3B6lWDc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=pozSE0EBC6EBiBJpwiuPYlRHq+Y3pW1rqqQObL3pMo8v4VI/FPsmF44fS8nSlAOGA9lhibX9kCDH6dfiXqKXGwLrtf4t2uTI7HH/lUqYffWMG7OVUaH6rnpVNxD/idOgCrP/bmxByCOS47cD5DCgYOrg9HdFM7GTiZ95BhbUeCY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=MqMdtRRZ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="MqMdtRRZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 15AF5C4CEC5; Tue, 17 Sep 2024 13:47:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1726580835; bh=7y6lHUpzj4ENEmnHvaebsCoZS+iyBAZnVBKU3B6lWDc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MqMdtRRZV63AnQHWPtxOTGhHtWlxc1KhYE0chiME/JxAPNt0dL+J9PwCVMjLgITC3 JwVuprAk32FrR4PtfFncK/8RNYTSI0uIfqyQAk7IVrs9IR9bQd8qhyK4ACpNUxFble NCw4Joz4goylRplx33CNtvyZYwIoOq8hOWQyoiymF/EZ+7BDM00AoX/cLpNdu4zItA I01I0V5yKd21Z5yXy7+kjAN2rLwGopNRzEPF5DFB5XqzviNUBL6iktN/zqzifAqJlK r5B0tptlap2UpngcqoqQ1eluLD6uV/xZjZ+fMg+oR+T4HeVmd5b/fZQI/KaHS+fN65 i6BsaaAGgMpjA== Message-ID: Date: Tue, 17 Sep 2024 15:47:09 +0200 Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] drm/msm/a6xx+: Insert a fence wait before SMMU table update To: Rob Clark , dri-devel@lists.freedesktop.org Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, Akhil P Oommen , Connor Abbott , Rob Clark , Sean Paul , Konrad Dybcio , Abhinav Kumar , Dmitry Baryshkov , Marijn Suijten , David Airlie , Daniel Vetter , open list References: <20240913195132.8282-1-robdclark@gmail.com> Content-Language: en-US From: Konrad Dybcio In-Reply-To: <20240913195132.8282-1-robdclark@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 13.09.2024 9:51 PM, Rob Clark wrote: > From: Rob Clark > > The CP_SMMU_TABLE_UPDATE _should_ be waiting for idle, but on some > devices (x1-85, possibly others), it seems to pass that barrier while > there are still things in the event completion FIFO waiting to be > written back to memory. Can we try to force-fault around here on other GPUs and perhaps limit this workaround? Akhil, do we have any insight on this? Konrad