1. 14 6月, 2016 3 次提交
  2. 10 6月, 2016 1 次提交
  3. 09 6月, 2016 28 次提交
  4. 03 6月, 2016 3 次提交
    • O
      drm/amdkfd: print once about mem_banks truncation · 0fbbbf8b
      Oded Gabbay 提交于
      This print can really spam the kernel log in case we are truncating
      mem_banks, so just print this info once. It should also not be classified
      as warning.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      0fbbbf8b
    • O
      drm/amdkfd: destroy dbgmgr in notifier release · bc4755a4
      Oded Gabbay 提交于
      amdkfd need to destroy the debug manager in case amdkfd's notifier
      function is called before the unbind function, because in that case,
      the unbind function will exit without destroying debug manager.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      CC: Stable <stable@vger.kernel.org>
      bc4755a4
    • O
      drm/amdkfd: unbind only existing processes · 121b78e6
      Oded Gabbay 提交于
      When unbinding a process from a device (initiated by amd_iommu_v2), the
      driver needs to make sure that process still exists in the process table.
      There is a possibility that amdkfd's own notifier handler -
      kfd_process_notifier_release() - was called before the unbind function
      and it already removed the process from the process table.
      
      v2:
      Because there can be only one process with the specified pasid, and
      because *p can't be NULL inside the hash_for_each_rcu macro, it is more
      reasonable to just put the whole code inside the if statement that
      compares the pasid value. That way, when we exit hash_for_each_rcu, we
      simply exit the function as well.
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      CC: Stable <stable@vger.kernel.org>
      121b78e6
  5. 25 5月, 2016 3 次提交
  6. 24 5月, 2016 1 次提交
  7. 21 5月, 2016 1 次提交
    • D
      drm: Nuke ->vblank_disable_allowed · fcee5906
      Daniel Vetter 提交于
      This was added in
      
      commit 0a3e67a4
      Author: Jesse Barnes <jbarnes@virtuousgeek.org>
      Date:   Tue Sep 30 12:14:26 2008 -0700
      
          drm: Rework vblank-wait handling to allow interrupt reduction.
      
      to stay backwards-compatible with old UMS code that didn't even tell
      the kernel when it did a modeset, so that the kernel could
      save/restore vblank counters. At worst this means vblanks will be
      somewhat funky on a setup that very likely no one still runs.
      
      So let's just nuke it.
      
      Plan B would be to set it unconditionally in drm_vblank_init for kms
      drivers, instead of in each driver separately. So if this patch breaks
      anything please only restore the hunks in drmP.h and drm_irq.c, plus
      add a check for DRIVER_MODESET in drm_vblank_init.
      
      Stumbled over this in a discussion on irc with Chris.
      
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: Liviu Dudau <liviu.dudau@arm.com>
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
      Cc: Inki Dae <inki.dae@samsung.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Mark Yao <mark.yao@rock-chips.com>
      Cc: Sascha Hauer <s.hauer@pengutronix.de>
      Cc: Philipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      Acked-by: NLiviu Dudau <Liviu.Dudau@arm.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Tested-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      fcee5906