dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@amd.com>
To: David Airlie <airlied@linux.ie>
Cc: alexander.deucher@amd.com, dri-devel@lists.freedesktop.org
Subject: [PULL] drm-amdkfd-fixes
Date: Mon, 26 Jan 2015 12:44:04 +0200	[thread overview]
Message-ID: <20150126104404.GA19635@amd.com> (raw)

Hi Dave,

A couple of fixes for -rc7 in amdkfd:

- Forgot to free resources when creation of queue has failed
- Initialization of pipelines was incorrect (3 patches)

In addition, The patch "drm/amdkfd: Allow user to limit only queues per device" 
is not a fix, but I would like to push it for 3.19 as it changes the ABI 
between amdkfd and userspace (by changing the module parameters). I would 
prefer *not* to support the two deprecated module parameters if I don't have 
too, as amdkfd hasn't been released yet. 

However, if you think that this patch is not appropriate at this time, please 
remove it and I will prepare a new patch for 3.20 that keeps backward 
compatibility.

Thanks,

	Oded

The following changes since commit 26bc420b59a38e4e6685a73345a0def461136dce:

  Linux 3.19-rc6 (2015-01-25 20:04:41 -0800)

are available in the git repository at:

  git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-fixes-2015-01-26

for you to fetch changes up to 9fa843e76d9092e5348aac7252cbb71f09902507:

  drm/amdkfd: Fix bug in call to init_pipelines() (2015-01-22 12:50:37 +0200)

----------------------------------------------------------------
Ben Goz (1):
      drm/amdkfd: PQM handle queue creation fault

Oded Gabbay (4):
      drm/amdkfd: Allow user to limit only queues per device
      drm/radeon: Don't increment pipe_id in kgd_init_pipeline
      drm/amdkfd: Fix bug in pipelines initialization
      drm/amdkfd: Fix bug in call to init_pipelines()

 drivers/gpu/drm/amd/amdkfd/kfd_device.c            |  6 +-
 .../gpu/drm/amd/amdkfd/kfd_device_queue_manager.c  | 78 +++++++++++++++++++++-
 .../gpu/drm/amd/amdkfd/kfd_device_queue_manager.h  |  1 +
 drivers/gpu/drm/amd/amdkfd/kfd_module.c            | 27 +++-----
 drivers/gpu/drm/amd/amdkfd/kfd_pasid.c             |  2 +-
 drivers/gpu/drm/amd/amdkfd/kfd_priv.h              | 17 +++--
 .../gpu/drm/amd/amdkfd/kfd_process_queue_manager.c | 12 ++--
 drivers/gpu/drm/radeon/radeon_kfd.c                |  2 +-
 8 files changed, 106 insertions(+), 39 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-01-26 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 10:44 Oded Gabbay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-09 11:52 [PULL] drm-amdkfd-fixes Oded Gabbay
2016-06-03  5:58 Oded Gabbay
2016-01-28 13:03 Oded Gabbay
2015-07-09 10:30 Oded Gabbay
2015-06-16 12:45 Oded Gabbay
2015-06-03 18:58 Oded Gabbay
2015-05-07 15:38 Oded Gabbay
2015-03-19  8:22 Oded Gabbay
2015-02-23  8:58 Oded Gabbay
2015-02-02  8:11 Oded Gabbay
2015-01-13  8:03 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=20150126104404.GA19635@amd.com \
    --to=oded.gabbay@amd.com \
    --cc=airlied@linux.ie \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox