Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp3035764pxp; Tue, 8 Mar 2022 06:38:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJzjjI9mgtMwnsUqVPsPAuse2UJUsIanP6x0N6n3b5uUiYsIZXpUN+XqM3EyxF+X8qREaT8m X-Received: by 2002:a05:6a00:1950:b0:4f6:369b:4c4d with SMTP id s16-20020a056a00195000b004f6369b4c4dmr18573714pfk.79.1646750333523; Tue, 08 Mar 2022 06:38:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646750333; cv=none; d=google.com; s=arc-20160816; b=Gr2VExqDxE0zKNrpctOTZJGByc8XsdR+FO0DUm9h0jhmAf5SSojKHdd5yMzBPJzpvs PfleIXcA+dqEUlFmgUobOF68uc5L2EFWICmr7FUP4oeRXhrlRS1hI1DH8d0NDCanZot3 bwRoDAPDUhl4DPnViqmAFkRUEAlC2V3x4AXDBDiMFwu6qIIisAsV0beVRSISMdrlJBDs C3XPznEOhRNVK1h/I3v6TvP6l8deQ/imukiFogsEAerW46/L5tsdXkF2tigSqp7rpRKE lT2g11e6iTJJ2AHVZyqU6s6Ux0bvkkHAwiS+nICKwP5AmBpdxTToN+5clglV6QtCZ4Sm LMhw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=MYsPs8xhj3uUSUqVDGzRI++cBUeiCyq9zOOis/JQ6u0=; b=vYMHwLNgkpvDykLbZqrlIqspwmev5qqSsqp3lBZi7LvnjpBDudokKWyMN0SoPsLhFq 5aPJAKYlhf+hHvqYD0qr+Vtd+lNP5rnHwsBCpfzt6pRATNLsdp7HQCiYnLkknWiw616f k6yWeOfKh5DCUYbKiVayBZdti/URPrMYPEqZftLnPg1+q4vwIgyA+gMhTrFa9bkGPoEc mlp5sAXIhPpZtWrhoW0saTL4Pgyo0c+lFm5o2qHA+wpssIHadEER2bT4N8+8+VuNuRSt cQf0SwlI/bn4xW9BA0zgEPhxqpzsJJ+wEOSu+GWcG9UWpDtBpWNuqorT055skz4+tTuD xI+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=Jy5uYLZc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c3-20020a056a000ac300b004c1c36f4c71si16702208pfl.30.2022.03.08.06.38.36; Tue, 08 Mar 2022 06:38:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=Jy5uYLZc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345248AbiCHIwc (ORCPT + 99 others); Tue, 8 Mar 2022 03:52:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238022AbiCHIwV (ORCPT ); Tue, 8 Mar 2022 03:52:21 -0500 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [IPv6:2001:4b98:dc2:55:216:3eff:fef7:d647]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BD7440A02; Tue, 8 Mar 2022 00:51:16 -0800 (PST) Received: from [192.168.1.111] (91-156-85-209.elisa-laajakaista.fi [91.156.85.209]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id DA5C451C; Tue, 8 Mar 2022 09:51:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1646729473; bh=tx1v41sFjwGQBvE+sIrqGvKblBFOQcSEb0qoE7wv6Xk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Jy5uYLZcwLb3KPsPqVod83/S0uNHXV1yFHxrkizv+pb8dLcTPQ5oNOd8pJzjzjund M0qFloP+xTpNuZPF/EVZbZy9fWLLv2IcCf3jZNUaJuhGWpbxmoVTk5iNfbqb2KmQW3 vy5SBv4M39NYY6ZYg3dSPMIjPZ3oWinmlBT9cQq8= Message-ID: Date: Tue, 8 Mar 2022 10:51:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH 0/3] drm: omapdrm: Fix excessive GEM buffers DMM/CMA usage Content-Language: en-US To: Ivaylo Dimitrov , tomba@kernel.org Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, merlijn@wizzup.org, tony@atomide.com, airlied@linux.ie, daniel@ffwll.ch References: <1642587791-13222-1-git-send-email-ivo.g.dimitrov.75@gmail.com> <47dbc690-bff2-8839-f01f-9287403a7562@gmail.com> From: Tomi Valkeinen In-Reply-To: <47dbc690-bff2-8839-f01f-9287403a7562@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/02/2022 18:21, Ivaylo Dimitrov wrote: > Hi Tomi, > > On 17.02.22 г. 15:03 ч., Tomi Valkeinen wrote: >> Hi Ivaylo, >> >> On 19/01/2022 12:23, Ivaylo Dimitrov wrote: >>> This patch series fixes excessive DMM or CMA usage of GEM buffers >>> leading to >>> various runtime allocation failures. The series enables daily usage >>> of devices >>> without exausting limited resources like CMA or DMM space if GPU >>> rendering is >>> needed. >>> >>> The first patch doesn't bring any functional changes, it just moves some >>> TILER/DMM related code to a separate function, to simplify the review >>> of the >>> next two patches. >>> >>> The second patch allows off-CPU rendering to non-scanout buffers. >>> Without that >>> patch, it is basically impossible to use the driver allocated GEM >>> buffers on >>> OMAP3 for anything else but a basic CPU rendered examples as if we >>> want GPU >>> rendering, we must allocate buffers as scanout buffers, which are CMA >>> allocated. >>> CMA soon gets fragmented and we start seeing allocation failures. >>> Such failres >>> in Xorg cannot be handeled gracefully, so the system is basically >>> unusable. >>> >>> Third patch fixes similar issue on OMAP4/5, where DMM/TILER spaces get >>> fragmented with time, leading to allocation failures. >> >> I think this is just hacking around the problem. The problem is that >> omapdrm is being used by some as a generic buffer allocator. Those users > > Well, the user of omap_bo interface I know is xf86-video-omap. Unless if > by users you mean 'kernel users' which I know none. > > I think that if 'we' are to teach xorg omap DDX (or any other user in > that regard) to use GPU driver allocator for non-scanout buffers and > omapdrm for scanout, it will become a mess. Not impossible though, just > way more complicated than the $series. Also, why do omapdrm allow > allocation of non-linear buffers and CPU (userspace) access to them, but > refuses to export them to kernel drivers? Isn't that the whole point of > DMABUF stuff? This is not consistent to me. The series fixes that > inconsistency, nothing more. > >> should be changed to use a their own allocator or a generic allocator. > > SGX driver/userspace has and uses its own allocator, however, I think > there is more than that - what about TILER/VRFB? Do you say that SGX > userspace shall be smart enough to requests TILER buffers from omapdrm > when scanout buffer is requested and use its own allocator when not? All I'm saying is that omapdrm should not support allocating buffers that are not usable by the omapdrm hardware. It doesn't make any sense. > Actually I was thinking about something like that, and it is achievable > now we have: > > https://github.com/maemo-leste/sgx-ddk-um/blob/master/dbm/dbm.c (REed > SGX 1.17 ddk gbm backend) > >> And we could then drop the OMAP_BO_SCANOUT flag, as all buffers would >> be scanout buffers. >> > > And what about OMAP_BO_TILED_XX stuff? To me this is even more of a > hack, but it is what it is. Yes, I agree, I don't think those OMAP_BO_TILED_* values should be exposed to userspace. But I also agree to the "it is what it is" =). > Do I get it correctly that you want to get rid of omap_bo_new/_tiled and > have only dumb buffers available in omapdrm? TBH this would be great, > however I still don't see how a TILER/VRFB buffer would be allocated, > given that flags in drm_mode_create_dumb is not used anywhere in the > kernel(AFAIK). Unless all scanout buffers are allocated through > TILER/VRFB (which is a good idea IMO). We can't get rid of those as they're userspace API. >> Or do we have a regression in the driver? My understanding is that >> this has never really worked. >> > > There are couple of patches in omapdrm that change around BO flags and > their meaning so I think there is a regression, as the same > userspace/DDX on linux 5.9 results in only 2 linear buffers being > allocated, but as SGX driver has different version as well, I can't be > 100% sure without going through a lengthy assessment of SGX > driver/omapdrm code and patches since 5.9. Which I am not going to do as > I don't see what the benefit will be. > > Please consider this patch series as a fix to an inconsistency, as it is > merely that, it does not really bring any new functionality in terms of > what is allocated. I've considered, and I think I agree. The design of omapdrm + tiler is broken in my opinion, but it's there, it has userspace APIs, and it's all old code. It's probably not worth the effort to try to clean it up, while still somehow keeping the old userspace working. I've had these patchesin my work branch for a while and I haven't seen any issues. I'll keep them there for a bit longer and I'll look at these patches a bit more, but I think I'll merge them at some point. Tomi