From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: [pull] radeon drm-next-3.15
Date: Tue, 04 Mar 2014 14:51:08 +0100 [thread overview]
Message-ID: <5315DA4C.3090705@vodafone.de> (raw)
Hi Dave,
this is the second pull request for 3.15 radeon changes. Highlights this
time:
- Better VRAM usage
- VM page table rework
- Enabling different UVD clocks again
- Some general cleanups and improvements
The following changes since commit 4d538b79197901fecc42e746d515d07fd1089b62:
Merge branch 'drm-next-3.15' of
git://people.freedesktop.org/~deathsimple/linux into drm-next
(2014-02-27 14:39:30 +1000)
are available in the git repository at:
git://people.freedesktop.org/~deathsimple/linux drm-next-3.15
for you to fetch changes up to df0af4403aa8df728a62ccb62a61b3244871068f:
drm/radeon: remove struct radeon_bo_list (2014-03-04 14:34:34 +0100)
----------------------------------------------------------------
Alex Deucher (1):
drm/radeon: use variable UVD clocks
Christian König (10):
drm/radeon: improve ring lockup detection code v2
drm/radeon: cleanup the fence ring locking code
drm/radeon: fix missing bo reservation
drm/radeon: fix VCE suspend/resume
drm/radeon: separate gart and vm functions
drm/radeon: further cleanup vm flushing & fencing
drm/radeon: use normal BOs for the page tables v4
drm/radeon: remove global vm lock
drm/radeon: drop non blocking allocations from sub allocator
drm/radeon: remove struct radeon_bo_list
Marek Olšák (6):
drm/radeon: add a way to get and set initial buffer domains v2
drm/radeon: track memory statistics about VRAM and GTT usage and
buffer moves v2
drm/radeon: deduplicate code in radeon_gem_busy_ioctl
drm/radeon: add buffers to the LRU list from smallest to largest
drm/radeon: validate relocations in the order determined by
userspace v3
drm/radeon: limit how much memory TTM can move per IB according
to VRAM usage
drivers/gpu/drm/radeon/Makefile | 2 +-
drivers/gpu/drm/radeon/evergreen_cs.c | 210 ++++++++++-----------
drivers/gpu/drm/radeon/r100.c | 40 ++--
drivers/gpu/drm/radeon/r200.c | 20 +-
drivers/gpu/drm/radeon/r300.c | 32 ++--
drivers/gpu/drm/radeon/r600_cs.c | 110 +++++------
drivers/gpu/drm/radeon/radeon.h | 61 +++---
drivers/gpu/drm/radeon/radeon_cs.c | 156 ++++++++++++----
drivers/gpu/drm/radeon/radeon_device.c | 8 +-
drivers/gpu/drm/radeon/radeon_drv.c | 3 +-
drivers/gpu/drm/radeon/radeon_fence.c | 59 +-----
drivers/gpu/drm/radeon/radeon_gart.c | 958
-----------------------------------------------------------------------------------------------
drivers/gpu/drm/radeon/radeon_gem.c | 49 +++--
drivers/gpu/drm/radeon/radeon_kms.c | 26 ++-
drivers/gpu/drm/radeon/radeon_object.c | 135 ++++++++++++--
drivers/gpu/drm/radeon/radeon_object.h | 9 +-
drivers/gpu/drm/radeon/radeon_pm.c | 7 +-
drivers/gpu/drm/radeon/radeon_ring.c | 50 ++---
drivers/gpu/drm/radeon/radeon_sa.c | 7 +-
drivers/gpu/drm/radeon/radeon_semaphore.c | 14 +-
drivers/gpu/drm/radeon/radeon_ttm.c | 8 +-
drivers/gpu/drm/radeon/radeon_uvd.c | 5 +-
drivers/gpu/drm/radeon/radeon_vce.c | 65 ++++---
drivers/gpu/drm/radeon/radeon_vm.c | 966
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/uapi/drm/radeon_drm.h | 15 ++
25 files changed, 1623 insertions(+), 1392 deletions(-)
create mode 100644 drivers/gpu/drm/radeon/radeon_vm.c
next reply other threads:[~2014-03-04 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 13:51 Christian König [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-09 9:55 [pull] radeon drm-next-3.15 Christian König
2014-04-18 18:22 ` Alex Deucher
2014-04-03 10:48 Christian König
2014-03-25 12:32 Christian König
2014-02-18 18:32 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=5315DA4C.3090705@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=airlied@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.