From: Oded Gabbay <oded.gabbay@amd.com>
To: airlied@gmail.com, dri-devel@lists.freedesktop.org
Cc: alexander.deucher@amd.com, Dana.Elifaz@amd.com
Subject: [PULL] amdkfd-fixes
Date: Tue, 23 Dec 2014 23:40:14 +0200 [thread overview]
Message-ID: <20141223214014.GA8603@amd.com> (raw)
Hi Dave,
Two fixes for amdkfd.
- Display MEC fw version in topology. Without this, the HSA userspace
stack is broken.
- Init apertures information only once per process
The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
are available in the git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/amdkfd-fixes-2014-12-23
for you to fetch changes up to dd59239a9862a42e4b8d47e4aaa8d595d08c29ab:
amdkfd: init aperture once per process (2014-11-18 13:56:23 +0200)
----------------------------------------------------------------
Alexey Skidanov (1):
amdkfd: init aperture once per process
Oded Gabbay (3):
drm/amd: Add get_fw_version to kfd-->kgd interface
drm/radeon: Add implementation of get_fw_version
amdkfd: Display MEC fw version in topology node
drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 4 --
drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c | 6 +--
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 9 +++++
drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 8 +++-
drivers/gpu/drm/amd/include/kgd_kfd_interface.h | 15 +++++++
drivers/gpu/drm/radeon/radeon_kfd.c | 53 +++++++++++++++++++++++++
6 files changed, 85 insertions(+), 10 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-23 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 21:40 Oded Gabbay [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 19:35 [PULL] amdkfd-fixes Oded Gabbay
2015-01-06 17:09 Oded Gabbay
2015-01-06 17:18 ` Oded Gabbay
2015-01-06 17:37 ` 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=20141223214014.GA8603@amd.com \
--to=oded.gabbay@amd.com \
--cc=Dana.Elifaz@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.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.