From: Daniel Vetter <daniel@ffwll.ch>
To: "Asahi Lina" <lina@asahilina.net>,
"Christian König" <christian.koenig@amd.com>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Dave Airlie" <airlied@gmail.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
andrey.grodzovsky@amd.com, tvrtko.ursulin@linux.intel.com,
"Matthew Brost" <matthew.brost@intel.com>,
yuq825@gmail.com,
"Boris Brezillon" <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Regression] drm/scheduler: track GPU active time per entity
Date: Thu, 6 Apr 2023 19:46:34 +0200 [thread overview]
Message-ID: <ZC8FetzkowU4Q59K@phenom.ffwll.local> (raw)
In-Reply-To: <ZC8ElEkZEp1TGZJg@phenom.ffwll.local>
On Thu, Apr 06, 2023 at 07:42:44PM +0200, Daniel Vetter wrote:
> But I think there's tools to make sure we don't dig a complete hole with
> these it sounds like. I guess another topic for pestering the rust folks.
Or to put it very bluntly: Could we make Arc<T> at least runtime enforce
(with the usual lockdep annotation trick like fs_reclaim) that and Drop is
the final one?
If that's the rust Arc<T> linux semantics then I think my worries are 100%
covered. And we'll sort out the trickier type based enforcement for
special cases when they hit us.
The downside is that this is substantially stricter than kref on the C
side, but I think that's a Good Thing :-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-04-06 17:46 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 0:57 [Regression] drm/scheduler: track GPU active time per entity Danilo Krummrich
2023-03-28 8:54 ` Lucas Stach
2023-04-04 4:31 ` Luben Tuikov
2023-04-05 14:05 ` Danilo Krummrich
2023-04-05 14:05 ` Danilo Krummrich
2023-04-05 16:09 ` Luben Tuikov
2023-04-05 16:09 ` Luben Tuikov
2023-04-05 16:23 ` Danilo Krummrich
2023-04-05 16:23 ` Danilo Krummrich
2023-04-06 8:22 ` Christian König
2023-04-06 8:22 ` Christian König
2023-04-06 8:27 ` Daniel Vetter
2023-04-06 8:27 ` Daniel Vetter
2023-04-06 9:05 ` Asahi Lina
2023-04-06 9:05 ` Asahi Lina
2023-04-06 10:09 ` Daniel Vetter
2023-04-06 10:09 ` Daniel Vetter
2023-04-06 12:21 ` Asahi Lina
2023-04-06 12:21 ` Asahi Lina
2023-04-06 13:37 ` Daniel Vetter
2023-04-06 13:37 ` Daniel Vetter
2023-04-06 14:43 ` Asahi Lina
2023-04-06 14:43 ` Asahi Lina
2023-04-06 15:30 ` Daniel Vetter
2023-04-06 15:30 ` Daniel Vetter
2023-04-06 17:11 ` Asahi Lina
2023-04-06 17:11 ` Asahi Lina
2023-04-06 17:42 ` Daniel Vetter
2023-04-06 17:42 ` Daniel Vetter
2023-04-06 17:46 ` Daniel Vetter [this message]
2023-04-06 10:45 ` Lucas Stach
2023-04-06 10:45 ` Lucas Stach
2023-04-06 12:09 ` Daniel Vetter
2023-04-06 12:09 ` Daniel Vetter
2023-04-06 12:19 ` Lucas Stach
2023-04-06 12:19 ` Lucas Stach
2023-04-06 13:56 ` Daniel Vetter
2023-04-06 13:56 ` Daniel Vetter
2023-04-06 14:21 ` Christian König
2023-04-06 14:21 ` Christian König
2023-04-06 15:24 ` Lucas Stach
2023-04-06 15:24 ` Lucas Stach
2023-04-06 15:33 ` Christian König
2023-04-06 15:33 ` Christian König
2023-04-06 15:59 ` Daniel Vetter
2023-04-06 15:59 ` Daniel Vetter
2023-04-06 16:23 ` Daniel Vetter
2023-04-06 16:23 ` Daniel Vetter
2023-04-06 22:36 ` Luben Tuikov
2023-04-06 22:36 ` Luben Tuikov
2023-04-06 22:30 ` Luben Tuikov
2023-04-06 22:30 ` Luben Tuikov
2023-04-05 17:44 ` Lucas Stach
2023-04-05 20:44 ` Luben Tuikov
2023-04-06 15:58 ` Lucas Stach
2023-04-06 22:06 ` Luben Tuikov
[not found] <e3e07282-136f-5239-96ae-4aeb2d3c95d7.ref@yahoo.de>
2023-03-28 0:54 ` Danilo Krummrich
2023-03-28 10:29 ` Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZC8FetzkowU4Q59K@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=andrey.grodzovsky@amd.com \
--cc=bagasdotme@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=matthew.brost@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=yuq825@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.