| created | 2020-11-27T03:49:39Z |
|---|---|
| begin | 2020-09-16T00:00:00Z |
| end | 2020-09-17T00:00:00Z |
| path | src/sys |
| commits | 7 |
| date | 2020-09-16T00:00:40Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_tc.c | log | diff | annotate |
| message |
timecounting: provide a naptime variable for userspace via kvm_read(3) vmstat(8) uses kvm_read(3) to extract the naptime from the kernel. Problem is, I deleted `naptime' from the global namespace when I moved it into the timehands. This patch restores it. It gets updated from tc_windup(). Only userspace should use it, and only when the kernel is dead. We need to tweak a variable in tc_setclock() to avoid shadowing the (once again) global naptime. |
|||
| date | 2020-09-16T08:01:15Z | |||
|---|---|---|---|---|
| author | mpi | |||
| files | src/sys/sys/proc.h | log | diff | annotate |
| message |
Document that `p_siglist' and `p_sigmask' are updated via atomics. ok claudio@ |
|||
| date | 2020-09-16T08:02:53Z | |||
|---|---|---|---|---|
| author | deraadt | |||
| files | src/sys/kern/kern_pledge.c | log | diff | annotate |
| message |
As discovered by kettenis, recent mesa wants sysctl hw.physmem64, and in pledged programs that is unfortable. My snark levels are a bit drained, but I must say I'm always dissapointed when programs operating on virtual resources enquire about total physical resource availability, the only reason to ask is so they can act unfair relative to others in the shared environment. SIGH. |
|||
| date | 2020-09-16T09:35:14Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/dev/acpi/abl.c | log | diff | annotate |
| message |
Add a command explaining that this driver uses the ACPI SMI command port and why we need magic to map it. |
|||
| date | 2020-09-16T10:06:56Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/kern/kern_pledge.c | log | diff | annotate |
| message |
put HW_PHYSMEM64 case under CTL_HW not CTL_KERN Fixes previous. Problem spotted by kettenis@ |
|||
| date | 2020-09-16T11:52:17Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/acpi/acpivout.c | log | diff | annotate |
| src/sys/dev/acpi/dsdt.c | log | diff | annotate | |
| src/sys/dev/acpi/dsdt.h | log | diff | annotate | |
| message |
disable acpivout brightness control on machines aware of Windows 8 On a HP ProBook 650 G1 acpivout backlight brightness control only works if we don't claim to be Windows 8. If we don't claim to be Windows 8 _BCL gives 21 levels with increments of 5, otherwise 101 levels (0-100) and a _BCM that does nothing. This is related to requirements Microsoft has for Windows 8 and later hardware certification. Having acpivout not fully attach lets inteldrm handle brightness ioctls. Brightness control via physical buttons will require a new acpi driver for the HP flavour of WMI. Add Windows 10 2004 _OSI value to the list while here. ok mpi@ kmos@ on an earlier version tested by kmos@ on 6460b and 6470b ProBooks which had the same problem feedback and ok kettenis@ |
|||
| date | 2020-09-16T13:50:42Z | |||
|---|---|---|---|---|
| author | mpi | |||
| files | src/sys/kern/kern_pledge.c | log | diff | annotate |
| src/sys/kern/kern_proc.c | log | diff | annotate | |
| src/sys/kern/kern_sig.c | log | diff | annotate | |
| src/sys/sys/signalvar.h | log | diff | annotate | |
| message |
Move duplicated code to send an uncatchable SIGABRT into a function. ok claudio@ |
|||