Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 16 2月, 2012 5 次提交
  3. 14 2月, 2012 3 次提交
  5. 09 2月, 2012 2 次提交
  7. 07 2月, 2012 1 次提交
  9. 03 2月, 2012 2 次提交
  11. 02 2月, 2012 3 次提交
  13. 01 2月, 2012 8 次提交
  15. 30 1月, 2012 4 次提交
  17. 29 1月, 2012 1 次提交
  19. 28 1月, 2012 1 次提交
  21. 27 1月, 2012 5 次提交
  23. 26 1月, 2012 2 次提交
    • B
      drm/ttm: fix two regressions since move_notify changes · 9f1feed2
      由 Ben Skeggs 提交于 
      Both changes in dc97b340 cause serious
regressions in the nouveau driver.

move_notify() was originally able to presume that bo->mem is the old node,
and new_mem is the new node.  The above commit moves the call to
move_notify() to after move() has been done, which means that now, sometimes,
new_mem isn't the new node at all, bo->mem is, and new_mem points at a
stale, possibly-just-been-killed-by-move node.

This is clearly not a good situation.  This patch reverts this change, and
replaces it with a cleanup in the move() failure path instead.

The second issue is that the call to move_notify() from cleanup_memtype_use()
causes the TTM ghost objects to get passed into the driver.  This is clearly
bad as the driver knows nothing about these "fake" TTM BOs, and ends up
accessing uninitialised memory.

I worked around this in nouveau's move_notify() hook by ensuring the BO
destructor was nouveau's.  I don't particularly like this solution, and
would rather TTM never pass the driver these objects.  However, I don't
clearly understand the reason why we're calling move_notify() here anyway
and am happy to work around the problem in nouveau instead of breaking the
behaviour expected by other drivers.
Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
Reviewed-by: NThomas Hellstrom <thellstrom@vmware.com>
Cc: Jerome Glisse <j.glisse@gmail.com>
Signed-off-by: NDave Airlie <airlied@redhat.com>
      9f1feed2
    • D
      drm/i915: fixup forcewake spinlock fallout in drpc debugfs function · 93b525dc
      由 Daniel Vetter 提交于 
      My forcewake spinlock patches have a functional conflict with Ben
Widawsky's gen6 drpc support for debugfs. Result was a benign warning
about trying to read an non-atomic variabla with atomic_read.

Note that the entire check is racy anyway and purely informational.
Also update it to reflect the forcewake voodoo changes, the kernel can
now also hold onto a forcewake reference for longer times.
Signed-Off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: NBen Widawsky <ben@bwidawsk.net>
Signed-off-by: NKeith Packard <keithp@keithp.com>
      93b525dc
  25. 25 1月, 2012 3 次提交