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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0ACB4CA0EC5 for ; Mon, 11 Sep 2023 21:41:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237230AbjIKVj0 (ORCPT ); Mon, 11 Sep 2023 17:39:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52936 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243990AbjIKShz (ORCPT ); Mon, 11 Sep 2023 14:37:55 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF4171AB for ; Mon, 11 Sep 2023 11:37:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1694457470; x=1725993470; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=ocrIL0ZlmVpB256Jk07u6tj77vPtfJwjxZjpXnxO1+4=; b=Es3LehkfS2NIaNhLIStnTk/zYDbVVIvuk2NLkuKbEnW/hJwv8BUzQRHL bT7/Y3fXO0RGs9lIUCV3b6DtWznq86r1q/yYwh4knRtIhmWt2oRBXSce/ uKlvaX6/DMyLaBl47Eczy8Y+EucX7nXIBuiKB7jYbGUDW0iSTKhvOXtxo qBNeessydjrhAorK92aenq+QFdZRV1ob9dRXw24SEWixDGFFnQX7z/1+b 2spUAvk7VP7/jN8X5Nram91j0A28eSkluLXbsbwlLQU02xsptGUQio8+V q40I1rOqFDT9vekxwmmMxxPAyMbll8Fl6+VjmO06GGkPNS6/z9ppMg6n2 w==; X-IronPort-AV: E=McAfee;i="6600,9927,10830"; a="377080344" X-IronPort-AV: E=Sophos;i="6.02,244,1688454000"; d="scan'208";a="377080344" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Sep 2023 11:37:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10830"; a="867051091" X-IronPort-AV: E=Sophos;i="6.02,244,1688454000"; d="scan'208";a="867051091" Received: from lbinmo2x-mobl1.gar.corp.intel.com (HELO [10.249.254.187]) ([10.249.254.187]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Sep 2023 11:37:46 -0700 Message-ID: Date: Mon, 11 Sep 2023 20:37:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [PATCH drm-misc-next v3 5/7] drm/gpuvm: add an abstraction for a VM / BO combination Content-Language: en-US To: Danilo Krummrich , airlied@gmail.com, daniel@ffwll.ch, matthew.brost@intel.com, sarah.walker@imgtec.com, donald.robson@imgtec.com, boris.brezillon@collabora.com, christian.koenig@amd.com, faith.ekstrand@collabora.com Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20230909153125.30032-1-dakr@redhat.com> <20230909153125.30032-6-dakr@redhat.com> <0a8799c3-1d4c-8d87-ebca-013f6541fbc4@linux.intel.com> <06bbb49d-974f-e3bb-f844-1509313066cc@redhat.com> From: =?UTF-8?Q?Thomas_Hellstr=c3=b6m?= In-Reply-To: <06bbb49d-974f-e3bb-f844-1509313066cc@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/11/23 19:49, Danilo Krummrich wrote: > Hi Thomas, > > On 9/11/23 19:19, Thomas Hellström wrote: >> Hi, Danilo >> >> On 9/9/23 17:31, Danilo Krummrich wrote: >>> This patch adds an abstraction layer between the drm_gpuva mappings of >>> a particular drm_gem_object and this GEM object itself. The abstraction >>> represents a combination of a drm_gem_object and drm_gpuvm. The >>> drm_gem_object holds a list of drm_gpuvm_bo structures (the structure >>> representing this abstraction), while each drm_gpuvm_bo contains >>> list of >>> mappings of this GEM object. >>> >>> This has multiple advantages: >>> >>> 1) We can use the drm_gpuvm_bo structure to attach it to various lists >>>     of the drm_gpuvm. This is useful for tracking external and evicted >>>     objects per VM, which is introduced in subsequent patches. >>> >>> 2) Finding mappings of a certain drm_gem_object mapped in a certain >>>     drm_gpuvm becomes much cheaper. >>> >>> 3) Drivers can derive and extend the structure to easily represent >>>     driver specific states of a BO for a certain GPUVM. >>> >>> The idea of this abstraction was taken from amdgpu, hence the credit >>> for >>> this idea goes to the developers of amdgpu. >>> >>> Cc: Christian König >>> Signed-off-by: Danilo Krummrich >> >> Did you consider having the drivers embed the struct drm_gpuvm_bo in >> their own bo definition? I figure that would mean using the gem bo's >> refcounting and providing a helper to call from the driver's bo >> release. Looks like that could potentially save a lot of code? Or is >> there something that won't work with that approach? > > There are drm_gpuvm_ops::vm_bo_alloc and drm_gpuvm_ops::vm_bo_free > callback for drivers to register for that purpose. Ah OK. Thanks, I'll take a deeper look. /Thomas > > - Danilo > >> >> Thanks, >> >> Thomas >> >> >