From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Zack Rusin <zackr@vmware.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "dakr@redhat.com" <dakr@redhat.com>,
"arunpravin.paneerselvam@amd.com"
<arunpravin.paneerselvam@amd.com>
Subject: Re: [PATCH 9/9] drm: move ttm_execbuf_util into vmwgfx
Date: Wed, 8 Mar 2023 10:10:20 +0100 [thread overview]
Message-ID: <6933b07b-af79-5350-b161-12ee73732b30@gmail.com> (raw)
In-Reply-To: <b4beeee4b2a004938adc6c502443f7b3311aad50.camel@vmware.com>
Am 08.03.23 um 06:14 schrieb Zack Rusin:
> On Tue, 2023-02-28 at 09:34 +0100, Christian König wrote:
>> VMWGFX is the only remaining user of this and should probably moved over
>> to drm_exec when it starts using GEM as well.
> Is this because vmwgfx piggybacks buffer-id relocations on top of ttm validations or
> did you just find it too hard to port it over? I'd prefer to avoid ttm moves to
> vmwgfx and at least have a clear idea of what we need to do to port.
I've just found it to hard to port it over because vmwgfx does some
strange things with the validation code here.
If you want we can take a deeper look at this together, but I need to
find some time.
Alternatively just tell me how to do it and I will add that to the patch
set :)
Regards,
Christian.
>
> z
next prev parent reply other threads:[~2023-03-08 9:10 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 [this message]
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 ` Common DRM execution context v3 Danilo Krummrich
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=6933b07b-af79-5350-b161-12ee73732b30@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arunpravin.paneerselvam@amd.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=zackr@vmware.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.