drm: Update to Linux 4.15.18

* Create /dev/dri/renderD* devices
Generally handle /dev entries creation as close to Linux as possible.

* Add drm master support
Sync authentification code with Li

drm: Update to Linux 4.15.18

* Create /dev/dri/renderD* devices
Generally handle /dev entries creation as close to Linux as possible.

* Add drm master support
Sync authentification code with Linux 4.15.18

* handle vm_mm->mmap_sem in ttm page fault operations

* Update dma-fence code from OpenBSD

* This commit contains sleep/wakeup and other changes
from Matthew Dillon <dillon@apollo.backplane.com>

show more ...

drm/linux: Fix complete() and complete_all()

Completion counters are supposed to be bounded by UINT_MAX.

drm/linux: Add wait_for_completion()

drm: Remove most system headers from linux/list.h

They do not serve any useful purpose there.

Suggested-by: zrj

drm/linux: Add or improve various header files

drm/linux: Add reinit_completion()

drm: Use lockmgr locks with Linux wait queues

* On Linux, it is possible to grab a second spinlock in an already
spinlock-protected code section.

* The wait_event() macro is used in such a situat

drm: Use lockmgr locks with Linux wait queues

* On Linux, it is possible to grab a second spinlock in an already
spinlock-protected code section.

* The wait_event() macro is used in such a situation in the i915 driver.
One of the event checks itself tries to grab a second lock. What's more,
this second lock is a lockmgr lock in the DragonFly kernel. This results
in the following situation:

spinlock
lockmgr LK_EXCLUSIVE
spinunlock

* Unfortunately if the lockmgr lock can't be acquired, the thread is put
to sleep and a thread sleeping with a spinlock held leads to a general
system freeze or a kernel panic.

* For that reason, we can't use a spinlock in Linux wait queues. Change
the internal wait_queue_head_t lock to a lockmgr lock.

Thanks go to Imre Vadász for spotting this horrible issue.

show more ...

drm: Use the ERESTARTSYS error code

* Linux kernel functions can return -ERESTARTSYS in some cases, a
negative value indicating an error (typically -512)

* Howewer, ERESTARTSYS was previously as

drm: Use the ERESTARTSYS error code

* Linux kernel functions can return -ERESTARTSYS in some cases, a
negative value indicating an error (typically -512)

* Howewer, ERESTARTSYS was previously as ERESTART, itself defined
as -1 in *BSD kernels

* The -ERESTARTSYS return value thus was positive on the DragonFly
kernel, potentially breaking various drm error checks.

* Fix this issue by defining ERESTARTSYS separately

Thanks-to: Imre Vadasz for discovering the original problem

show more ...

kernel - Move wakeup*() to ouside a spin lock

* Move the wakeup*() calls in the linux completion interface from inside
to outside the spinlock. It can't be safely called from inside the
spinloc

kernel - Move wakeup*() to ouside a spin lock

* Move the wakeup*() calls in the linux completion interface from inside
to outside the spinlock. It can't be safely called from inside the
spinlock.

Reported-by: me_

show more ...

drm: Add a linux/completion.h implementation

* The drm/i915 code expect completion to be a struct containing a
counter named 'done' and a wait queue named 'wait'

* It also expects this wait queue

drm: Add a linux/completion.h implementation

* The drm/i915 code expect completion to be a struct containing a
counter named 'done' and a wait queue named 'wait'

* It also expects this wait queue to be a struct containing a spinlock
named 'lock'. Adjust the implementation in linux/wait.h accordingly.

show more ...