wireguard-openbsd/sys/dev/pci/drm, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/pci/drm?h=master2021-03-05T12:40:13Zansi2021-03-05T12:40:13Zjsgjsg@openbsd.org2021-03-05T12:40:13Zurn:sha1:c42d7d40986d86fb44de3c2165faa17e501c546fremove warning about amdgpu userptr ioctl being unimplemented2021-02-20T21:50:04Zjsgjsg@openbsd.org2021-02-20T21:50:04Zurn:sha1:ad2d38fa86fd2e27c36eb12497bcab3f0f6516fd
matches radeon and i915
reported by Benjamin Baier
correct drm work flush behaviour2021-02-14T03:42:55Zjsgjsg@openbsd.org2021-02-14T03:42:55Zurn:sha1:15e28df90169d92731a148fca7d948f804296fe6
Don't set taskq to system_wq in INIT_WORK(). Test if taskq pointer is
non-NULL before calling taskq_barrier() in flush functions.
fixes a black screen on boot problem with 5.10.y drm using nano x1
bisected by jcs@ to
'drm/i915: Always flush the active worker before returning from the wait'
Simplify sleep_setup API to two operations in preparation for splitting2021-02-08T08:18:45Zmpimpi@openbsd.org2021-02-08T08:18:45Zurn:sha1:436960cf02775967604f33beab159c0cf4ade5a0
the SCHED_LOCK().
Putting a thread on a sleep queue is reduce to the following:
sleep_setup();
/* check condition or release lock */
sleep_finish();
Previous version ok cheloha@, jmatthew@, ok claudio@
revert drm vmalloc changes2021-01-13T01:04:49Zjsgjsg@openbsd.org2021-01-13T01:04:49Zurn:sha1:1673f09a40940493856db8f67271437f4f6e82d2
It is suspected they were to blame for a machine with inteldrm running X
(xterms and chromium) running out of resources after a few days.
ok kettenis@
Bring the emulated Linux memory allocation interfaces more in line with2021-01-08T23:02:09Zketteniskettenis@openbsd.org2021-01-08T23:02:09Zurn:sha1:2fb53b285c85042a93e33372b66fb452083680e6
what Linux does. Let vmalloc() use km_alloc(9) instead of malloc(9) and
let kvmalloc() only use malloc(9) for small (less than a page) allocations
and atomic allocations. This should reduce the pressure on the
"interrupt-safe" map.
ok jsg@
don't oversleep when waiting on fences2020-12-31T06:31:55Zjsgjsg@openbsd.org2020-12-31T06:31:55Zurn:sha1:19fc7f4fb4fca7a744885415ae7f07f446dc8644
original diff from and ok cheloha@
Refactor klist insertion and removal2020-12-25T12:59:51Zvisavisa@openbsd.org2020-12-25T12:59:51Zurn:sha1:9b0cf67b268a857fffa6a742ad6be57acdc35301
Rename klist_{insert,remove}() to klist_{insert,remove}_locked().
These functions assume that the caller has locked the klist. The current
state of locking remains intact because the kernel lock is still used
with all klists.
Add new functions klist_insert() and klist_remove() that lock the klist
internally. This allows some code simplification.
OK mpi@
sync with i915_pciids.h2020-12-20T04:13:12Zjsgjsg@openbsd.org2020-12-20T04:13:12Zurn:sha1:b5f7af6e96005bbfe7edbfb4250da450e1438b2edrm/i915: Remove dubious Valleyview PCI IDs2020-12-20T04:12:14Zjsgjsg@openbsd.org2020-12-20T04:12:14Zurn:sha1:75d7b50b0d8a50c81fe786ae49b095615d9d23a2
From Alexei Podtelezhnikov
f2bde2546b81b64fb58aa04888fdd82a090b3908 in mainline linux