From: j.glisse@gmail.com
To: dri-devel@lists.freedesktop.org
Cc: thellstrom@vmware.com
Subject: [RFC] ttm merge move/move_notify/invalidate_caches callback
Date: Thu, 5 Apr 2012 14:44:22 -0400 [thread overview]
Message-ID: <1333651466-4181-1-git-send-email-j.glisse@gmail.com> (raw)
This was discussed previously :
http://lists.freedesktop.org/archives/dri-devel/2012-January/018463.html
The plat de resistance is in patch4, the first 3 are simplification that
i believe can go as is.
Idea is that driver needs to know when ever a bo move happen and instead
of having 3 set of callback to allow driver to do things btw common ttm
move handling. Move the ttm move handling into each driver and let driver
customize it at appropriate point.
I intentionaly didn't not fully take advantage of that in neither radeon
or nouveau. ie i tried to keep the current code as much as possible so
one can see that i don't disrupt old behavior. There is opportunity to
simplify the move_notify driver function i believe.
I tested it on radeon and nouveau. This time i limited the 2G vram nvidia
gpu i have to behave like a 64M vram or 96M vram so i actually see the
vram eviction path being exercice while testing (this is why in my last
ttm patch set i missed the nouveau regression, again sorry about that).
So i am more confident that with this one i didn't regressed anything.
Thomas i tried to be carefull with vmwgfx but i didn't tested it. Only
built tested.
Cheers,
Jerome
next reply other threads:[~2012-04-05 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:44 j.glisse [this message]
2012-04-05 18:44 ` [PATCH 1/4] drm/ttm: simplify ttm_bo_move_ttm j.glisse
2012-04-05 18:44 ` [PATCH 2/4] drm/ttm: simplify ttm_bo_move_accel_cleanup remove useless arg j.glisse
2012-04-05 18:44 ` [PATCH 3/4] drm/ttm: simplify ttm_bo_move_memcpy " j.glisse
2012-04-05 18:44 ` [PATCH 4/4] drm/ttm: move bo move logic inside driver to avoid callback j.glisse
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=1333651466-4181-1-git-send-email-j.glisse@gmail.com \
--to=j.glisse@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).