From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 2ED2B18AE2; Mon, 22 Jun 2026 18:03:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782151402; cv=none; b=iiL5C3q8DCn88n215sSOvUzDBDUClo9rj8YJWvw4epTfHnb8z9ew75elo26uPGYex+DxzoLo+DLUqKKFaY34h0iomEgsdf8ShmWts1Izpc7qUdkc6Zh2PWp1w1d+QOSzhElDSgvkgU/y9biWC2bRxBdtRfAI0PGXaYBh7vLEptw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782151402; c=relaxed/simple; bh=K/GYJViJI5kalk51JPq0XHrSMDJTiy0e7Kj99pwes9w=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:To:From:Subject: References:In-Reply-To; b=LOSrqilk6howFRdDYV/IGkd6uzR15/vaBrjzmG8pEaIlYQrlLXxuWR7FRxawIk0YhrzXK2q+CMbQ6ZEFp7UMEMfRjk7wtfBdhVI8SuyBxzXPMqSdcCbS7dVsQFF4RybzGErnKRwlmD3+lDO8N2uHqAoPIH8LIxcaFWvuFX06iqU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=o0hae2ys; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="o0hae2ys" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 40AFB1F000E9; Mon, 22 Jun 2026 18:03:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782151400; bh=K/GYJViJI5kalk51JPq0XHrSMDJTiy0e7Kj99pwes9w=; h=Date:Cc:To:From:Subject:References:In-Reply-To; b=o0hae2yst0KDlG4ZR9ay16s4yZKGonAUKlyxERaHI50Xu5eRYE7b6dlmnHlmzig89 yKTn7X32AcWjy9kHvnAbez/lEAXY6QS+BdrBz1Spw4aLIRX8wAEQFsAEDPAny4QzsJ zisUTkeZrZ3XUVaWrmAu9H0Ym17ozWWvdHKDECcB/fcaYFkp+nAizmD+jqp6Mn47Wt aojMJmVg+ULCQhWLdlKiCjHWZhdOF1VBsDN1rZLFeaC0pcywq+AE/BAS8918TvSGz7 h+AkghBDZjAFWSZ8aGnm/lkF/qGUDxs6AJu+9uHA3JW1igbNigigWJobfO+gfDuPZH wl+/MmS2kIR0g== Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 22 Jun 2026 20:03:15 +0200 Message-Id: Cc: , , , , , , , , , , , , , , , , , To: "Lyude Paul" From: "Danilo Krummrich" Subject: Re: [PATCH v4 06/16] rust: drm: restrict AlwaysRefCounted to Normal GEM Object context References: <20260620184924.2247517-1-dakr@kernel.org> <20260620184924.2247517-7-dakr@kernel.org> In-Reply-To: On Mon Jun 22, 2026 at 7:52 PM CEST, Lyude Paul wrote: > Maybe there's a reason for you doing this I'm missing but, wouldn't it be= a > better idea to simply remove the DeviceContext generic from gem objects > entirely and instead always (with the exception of Ioctl callbacks, of co= urse) > just use the Normal context? I did consider that, but left it as a follow-up, since it is not directly related to this patch series to drop the DeviceContext from GEM objects entirely and I thought a discussion about whether to drop it entirely is be= tter suited for a separate patch. One thing I had in mind is that we could have TTM callbacks that guarantee = us a Registered DeviceContext that could be represented by the corresonding GEM object. Of course, it could also be represented by a separate &Device being passed to the callback. - Danilo