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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id DD1B5E6BF3C for ; Sat, 31 Jan 2026 00:16:22 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 39AB010E079; Sat, 31 Jan 2026 00:16:22 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.b="KrsG3FP9"; dkim-atps=neutral Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by gabe.freedesktop.org (Postfix) with ESMTPS id D44A810E109 for ; Sat, 31 Jan 2026 00:16:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1769818579; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=DUlHZCO3uYHyEV1uv7j6n5bPLjINc4Q3Eh1O4mdV7Bg=; b=KrsG3FP9pUkXOK12A3P5BXva0HYf9CQRbcnT8WtcN+7GDolMPCwToLZ+VGFhgo04AXunBZ R+I0OoN++WUFNsKM2URkK44OMABZ+ODL8/eShFYKdsYMH0J5tSEPx1goRci3GfH/7Jn95L pjtEkIubhVU4RMkA2rOaTmlg8vVAbf0= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-228-zlw75-UyNGmfOJGcqocEnw-1; Fri, 30 Jan 2026 19:16:16 -0500 X-MC-Unique: zlw75-UyNGmfOJGcqocEnw-1 X-Mimecast-MFC-AGG-ID: zlw75-UyNGmfOJGcqocEnw_1769818574 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 351AB180044D; Sat, 31 Jan 2026 00:16:14 +0000 (UTC) Received: from GoldenWind.lan (unknown [10.22.81.64]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 1676A18002A6; Sat, 31 Jan 2026 00:16:11 +0000 (UTC) From: Lyude Paul To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org, Danilo Krummrich Cc: nouveau@lists.freedesktop.org, "Miguel Ojeda" , "Simona Vetter" , "Alice Ryhl" , "Shankari Anand" , "David Airlie" , "Benno Lossin" , "Asahi Lina" , "Daniel Almeida" , "Lyude Paul" Subject: [PATCH v5 0/4] Introduce DeviceContext Date: Fri, 30 Jan 2026 19:13:29 -0500 Message-ID: <20260131001602.2095470-1-lyude@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Previous version of this patch series: https://patchwork.freedesktop.org/series/160217/#rev3 One of the unsolved issues we still have with the rust DRM bindings is the ability to limit certain Device operations to contexts where we can guarantee that a Device has been fully initialized and registered with userspace, or vice-versa (e.g. must be unregistered). While the previous solution for this that I had was simply not exposing drm::Device at all until the device has been registered with userspace, unfortunately this isn't enough since: * As we found out with Tyr, drivers occasionally need to be able to create GEM objects before device registration * We would still need to be able to handle KMS callbacks which could be invoked after KMS init but before userspace registration (not handled in this series specifically, but DeviceContext will be required for handling this). This patch series provides a pretty nice solution to this, by implementing a very similar solution to kernel::device::DeviceContext: introducing our own DeviceContext type state. This patch series depends on the two pre-requisite patch series: * https://patchwork.freedesktop.org/series/160523/ Series-wide changes V2: * s/DeviceCtx/DeviceContext/ for consistency * Move private driver-data availability to the Registration DeviceContext * s/AnyCtx/Init/ V4: * Split out DriverAllocImpl into it's own patch More changes described in each patch description. Lyude Paul (3): rust/drm: Introduce DeviceContext rust/drm: Don't setup private driver data until registration rust/drm/gem: Use DeviceContext with GEM objects Lyude Paul (4): rust/drm: Introduce DeviceContext rust/drm: Don't setup private driver data until registration rust/drm/gem: Add DriverAllocImpl type alias rust/drm/gem: Use DeviceContext with GEM objects drivers/gpu/drm/nova/driver.rs | 10 +- drivers/gpu/drm/nova/gem.rs | 11 +- drivers/gpu/drm/tyr/driver.rs | 12 +- drivers/gpu/drm/tyr/gem.rs | 3 +- rust/kernel/drm/device.rs | 250 +++++++++++++++++++++++++-------- rust/kernel/drm/driver.rs | 52 +++++-- rust/kernel/drm/gem/mod.rs | 64 ++++++--- rust/kernel/drm/mod.rs | 4 + 8 files changed, 305 insertions(+), 101 deletions(-) base-commit: cea7b66a80412e2a5b74627b89ae25f1d0110a4b prerequisite-patch-id: ddb20be75c8fc92ba2d48a5c4aa8e724202de1ff prerequisite-patch-id: 87e69cd89a806392d3275b19fbfb160d44d957c9 -- 2.52.0