From: Oded Gabbay <oded.gabbay@gmail.com>
To: airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: [PULL] drm-amdkfd-next-fixes
Date: Wed, 10 Jun 2015 15:26:27 +0300 [thread overview]
Message-ID: <20150610122627.GA8445@odedg-home.redhat.com> (raw)
Hi Dave,
A few fixes to the two pull requests you merged for 4.2:
- Make the reset wavefronts action be per process per device instead of
per process, because one device can be stuck but the other one won't be
- Add some missing properties to the CZ device_info structure
- Rename symbols to not have CONFIG_ prefix
- Some more cleanups and debug prints
Thanks,
Oded
The following changes since commit ae45577324d1f749c907840247d443696ac3bc7a:
virtgpu: include linux/types.h to avoid warning. (2015-06-05 12:31:12 +1000)
are available in the git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-next-fixes-2015-06-10
for you to fetch changes up to da73b9fb56c14c6d537738e891906006a7960535:
drm/amdkfd: remove not used defines from cik_regs.h (2015-06-06 22:26:47 +0300)
----------------------------------------------------------------
Ben Goz (1):
drm/amdkfd: make reset wavefronts per process per device
Oded Gabbay (3):
drm/amdkfd: add debug print to kfd_events.c
drm/amdkfd: Add missing properties to CZ device info
drm/amdkfd: remove not used defines from cik_regs.h
Valentin Rothberg (1):
drm/amdkfd: avoid CONFIG_ prefix for non-Kconfig symbols
drivers/gpu/drm/amd/amdkfd/cik_regs.h | 177 ++-------------------
drivers/gpu/drm/amd/amdkfd/kfd_dbgdev.c | 10 +-
drivers/gpu/drm/amd/amdkfd/kfd_dbgdev.h | 6 +-
drivers/gpu/drm/amd/amdkfd/kfd_device.c | 3 +
.../gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 7 +-
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 4 +
drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 10 +-
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 21 ++-
8 files changed, 53 insertions(+), 185 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-06-10 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 12:26 Oded Gabbay [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 12:13 [PULL] drm-amdkfd-next-fixes Oded Gabbay
2015-08-30 9:47 Oded Gabbay
2015-08-05 7:05 Oded Gabbay
2015-08-05 7:48 ` Daniel Vetter
2015-08-05 7:49 ` Oded Gabbay
2015-08-05 9:32 ` Daniel Vetter
2015-02-03 11:36 Oded Gabbay
2015-01-25 11:21 Oded Gabbay
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=20150610122627.GA8445@odedg-home.redhat.com \
--to=oded.gabbay@gmail.com \
--cc=airlied@linux.ie \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox