From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC302C433C1 for ; Tue, 23 Mar 2021 10:13:29 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8BBC06157E for ; Tue, 23 Mar 2021 10:13:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8BBC06157E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=intel-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 02D3E6E886; Tue, 23 Mar 2021 10:13:29 +0000 (UTC) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1792D6E0D1; Tue, 23 Mar 2021 10:13:27 +0000 (UTC) IronPort-SDR: wxatpHcl5lPVQs6FOjElyAwcnYynn4rkm9vYbMCuNZ6jEBxbohuTQbDfSUYh/ko6wASnBvaKKX XK9Bmf338fBg== X-IronPort-AV: E=McAfee;i="6000,8403,9931"; a="187130333" X-IronPort-AV: E=Sophos;i="5.81,271,1610438400"; d="scan'208";a="187130333" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Mar 2021 03:13:22 -0700 IronPort-SDR: b0d+r6O/4DJ/yDbi3Yqo+mOTVjT+xUw0DEzn2aGjHuStMlF9xwfzjcCr3lJESaPLZ4WT5RtgAO GwvESc5BywPA== X-IronPort-AV: E=Sophos;i="5.81,271,1610438400"; d="scan'208";a="414918003" Received: from wjlloyd-mobl2.ger.corp.intel.com (HELO localhost) ([10.252.53.124]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Mar 2021 03:13:14 -0700 From: Jani Nikula To: Daniel Vetter , DRI Development , Intel Graphics Development In-Reply-To: <20210323084453.366863-1-daniel.vetter@ffwll.ch> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20210323084453.366863-1-daniel.vetter@ffwll.ch> Date: Tue, 23 Mar 2021 12:13:11 +0200 Message-ID: <874kh25gaw.fsf@intel.com> MIME-Version: 1.0 Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: add gem/gt TODO X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Daniel Vetter , Dave Airlie , Daniel Vetter Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Tue, 23 Mar 2021, Daniel Vetter wrote: > We've discussed a bit how to get the gem/gt team better integrated > and collaborate more with the wider community and agreed to the > following: > > - all gem/gt patches are reviewed on dri-devel for now. That's > overkill, but in the past there was definitely too little of that. > > - i915-gem folks are encouraged to cross review core patches from > other teams > > - big features (especially uapi changes) need to be discussed in an > rfc patch that documents the interface and big picture design, > before we get lost in the details of the code > > - Also a rough TODO (can be refined as we go ofc) to get gem/gt back > on track, like we've e.g. done with DAL/DC to get that in shape. I personally think there should be a lower bar for discussing and editing the TODO items than via patches on the mailing list. Granted, the TODO file enforces the discussion happens at a large enough audience, but for at least some of the items I'd suggest filing gitlab issues [1], with todo label, and tracking there. BR, Jani. [1] https://gitlab.freedesktop.org/drm/intel/-/issues > > Cc: Jani Nikula > Cc: Joonas Lahtinen > Cc: Rodrigo Vivi > Cc: Jason Ekstrand > Cc: Dave Airlie > Signed-off-by: Daniel Vetter > --- > drivers/gpu/drm/i915/TODO.txt | 36 +++++++++++++++++++++++++++++++++++ > 1 file changed, 36 insertions(+) > create mode 100644 drivers/gpu/drm/i915/TODO.txt > > diff --git a/drivers/gpu/drm/i915/TODO.txt b/drivers/gpu/drm/i915/TODO.txt > new file mode 100644 > index 000000000000..d2e5bbb6339d > --- /dev/null > +++ b/drivers/gpu/drm/i915/TODO.txt > @@ -0,0 +1,36 @@ > +gem/gt TODO items > +----------------- > + > +- For discrete memory manager, merge enough dg1 to be able to refactor it to > + TTM. Then land pci ids (just in case that turns up an uapi problem). TTM has > + improved a lot the past 2 years, there's no reason anymore not to use it. > + > +- Come up with a plan what to do with drm/scheduler and how to get there. > + > +- There's a lot of complexity added past few years to make relocations faster. > + That doesn't make sense given hw and gpu apis moved away from this model years > + ago: > + 1. Land a modern pre-bound uapi like VM_BIND > + 2. Any complexity added in this area past few years which can't be justified > + with VM_BIND using userspace should be removed. Looking at amdgpu dma_resv on > + the bo and vm, plus some lru locks is all that needed. No complex rcu, > + refcounts, caching, ... on everything. > + This is the matching task on the vm side compared to ttm/dma_resv on the > + backing storage side. > + > +- i915_sw_fence seems to be the main structure for the i915-gem dma_fence model. > + How-to-dma_fence is core and drivers really shouldn't build their own world > + here, treating everything else as a fixed platform. i915_sw_fence concepts > + should be moved to dma_fence, drm/scheduler or atomic commit helpers. Or > + removed if dri-devel consensus is that it's not a good idea. Once that's done > + maybe even remove it if there's nothing left. > + > +Smaller things: > +- i915_utils.h needs to be moved to the right places. > + > +- dma_fence_work should be in drivers/dma-buf > + > +- i915_mm.c should be moved to the right places. Some of the helpers also look a > + bit fishy: > + > + https://lore.kernel.org/linux-mm/20210301083320.943079-1-hch@lst.de/ -- Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx