created | 2020-10-25T07:33:23Z |
---|---|
begin | 2020-10-20T00:00:00Z |
end | 2020-10-21T00:00:00Z |
path | src/sys |
commits | 7 |
date | 2020-10-20T04:22:17Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/drm_mm.c | log | diff | annotate |
src/sys/dev/pci/drm/drm_vma_manager.c | log | diff | annotate | |
src/sys/dev/pci/drm/i915/i915_gem.c | log | diff | annotate | |
src/sys/dev/pci/drm/i915/gem/i915_gem_execbuffer.c | log | diff | annotate | |
src/sys/dev/pci/drm/include/drm/drm_mm.h | log | diff | annotate | |
src/sys/dev/pci/drm/include/drm/drm_vma_manager.h | log | diff | annotate | |
src/sys/dev/pci/drm/include/linux/rbtree.h | log | diff | annotate | |
message |
use drm_mm from linux 5.7.y Without this boot time tests from setting amdgpu_testing = 1 fail. For example on Vega 56: drm: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF ... [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xa00000 [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0xb00000 ... [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x1fe00000 [drm] Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x1ff00000 [drm] *ERROR* 0xffff80000135f858 bind failed Error while testing BO move ok kettenis@ |
date | 2020-10-20T08:47:23Z | |||
---|---|---|---|---|
author | mpi | |||
files | src/sys/uvm/uvm_aobj.c | log | diff | annotate |
message |
Remove guard, uao_init() is called only once and no other function use one. ok kettenis@ |
date | 2020-10-20T15:21:44Z | |||
---|---|---|---|---|
author | visa | |||
files | src/sys/arch/mips64/mips64/trap.c | log | diff | annotate |
message |
Add handling for a trap instruction that terminates the process. OK deraadt@ |
date | 2020-10-20T15:26:59Z | |||
---|---|---|---|---|
author | visa | |||
files | src/sys/arch/mips64/mips64/lcore_access.S | log | diff | annotate |
message |
Use a trap instruction that unconditionally terminates the process. OK deraadt@ |
date | 2020-10-20T15:59:17Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/arch/alpha/alpha/machdep.c | log | diff | annotate |
src/sys/arch/loongson/dev/glx.c | log | diff | annotate | |
src/sys/arch/sh/sh/clock.c | log | diff | annotate | |
src/sys/arch/sparc64/sparc64/clock.c | log | diff | annotate | |
message |
alpha, loongson, sh, sparc64: recompute tick, tick_nsec when hz(9) is reset Normally we set hz(9) at compile-time in sys/conf/param.c to the value of HZ. HZ is one of the fundamental compilation options(4). However, sometimes we need to reset hz(9) at runtime. Whenever we reset hz(9) we need to recompute tick and tick_nsec. Otherwise a variety of "time stuff" in the kernel will not work correctly. For example, most timeouts will expire "too slow" or "too fast". There are a bunch of other places we use tick and tick_nsec that will exhibit similar problems. Test-compiled by deraadt@. |
date | 2020-10-20T22:37:12Z | |||
---|---|---|---|---|
author | cheloha | |||
files | src/sys/kern/kern_timeout.c | log | diff | annotate |
message | timeout(9): fix compilation under NKCOV |
date | 2020-10-20T23:21:41Z | |||
---|---|---|---|---|
author | patrick | |||
files | src/sys/arch/arm64/arm64/copystr.S | log | diff | annotate |
message |
copyout(9), copyinstr(9) and copyoutstr(9) should bail out properly if they are called with a length of 0. Found by our regression tests Debugged with deraadt@ ok kettenis@ |