From: Danilo Krummrich <dakr@redhat.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
arunpravin.paneerselvam@amd.com
Subject: Re: Common DRM execution context v3
Date: Tue, 28 Feb 2023 20:11:39 +0100 [thread overview]
Message-ID: <280bfe28-ee00-e765-b00e-0d3294dc6ef3@redhat.com> (raw)
In-Reply-To: <20230228083406.1720795-1-christian.koenig@amd.com>
Hi Christian,
On 2/28/23 09:33, Christian König wrote:
> Hi guys,
>
> thrid round for those patches. They have been in my queue for nearly a
> year now because I couldn't find much time to push into this.
>
> Danilo wants to use this for his GPU VAs tracker work and Arun needs it
> for hist secure semaphore work, so we should probably get it reviewed
> now.
Thanks for the follow up on this series - very much appreciated!
- Danilo
>
> Compared to the last version I've fixed one memory leak found by Danilo
> and removed the support for duplicate tracking. Only radeon really needs
> that and we can trivially handle it differently there.
>
> Please review and/or comment,
> Christian.
>
>
prev parent reply other threads:[~2023-02-28 19:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 8:33 Common DRM execution context v3 Christian König
2023-02-28 8:33 ` [PATCH 1/9] drm: execution context for GEM buffers v3 Christian König
2023-02-28 19:13 ` Danilo Krummrich
2023-03-02 7:49 ` Christian König
2023-03-03 13:45 ` Luben Tuikov
2023-03-03 14:11 ` Luben Tuikov
2023-03-10 10:42 ` Thomas Hellström (Intel)
2023-04-14 14:29 ` Francois Dugast
2023-02-28 8:33 ` [PATCH 2/9] drm: add drm_exec selftests Christian König
2023-02-28 8:34 ` [PATCH 3/9] drm/amdkfd: switch over to using drm_exec Christian König
2023-04-21 21:28 ` Felix Kuehling
2023-02-28 8:34 ` [PATCH 4/9] drm/amdgpu: use drm_exec for GEM and CSA handling Christian König
2023-02-28 8:34 ` [PATCH 5/9] drm/amdgpu: use drm_exec for MES testing Christian König
2023-02-28 8:34 ` [PATCH 6/9] drm/amdgpu: use the new drm_exec object for CS v2 Christian König
2023-02-28 8:34 ` [PATCH 7/9] drm/radeon: switch over to drm_exec Christian König
2023-02-28 16:45 ` kernel test robot
2023-02-28 16:45 ` kernel test robot
2023-02-28 8:34 ` [PATCH 8/9] drm/qxl: switch to using drm_exec Christian König
2023-02-28 16:03 ` kernel test robot
2023-02-28 16:03 ` kernel test robot
2023-02-28 16:34 ` kernel test robot
2023-02-28 16:34 ` kernel test robot
2023-02-28 8:34 ` [PATCH 9/9] drm: move ttm_execbuf_util into vmwgfx Christian König
2023-03-08 5:14 ` Zack Rusin
2023-03-08 9:10 ` Christian König
2023-03-09 5:14 ` Zack Rusin
2023-03-09 8:35 ` Thomas Hellström (Intel)
2023-03-09 8:26 ` Thomas Hellström (Intel)
2023-02-28 19:11 ` Danilo Krummrich [this message]
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=280bfe28-ee00-e765-b00e-0d3294dc6ef3@redhat.com \
--to=dakr@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arunpravin.paneerselvam@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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.