OpenBSD cvs log

created 2022-07-09T21:23:23Z
begin 2022-07-07T00:00:00Z
end 2022-07-08T00:00:00Z
path src/sys
commits 9

date 2022-07-07T00:56:46Z
author daniel
files src/sys/arch/i386/i386/locore0.S log diff annotate
src/sys/arch/i386/i386/machdep.c log diff annotate
src/sys/arch/i386/include/cputypes.h log diff annotate
src/sys/arch/i386/stand/libsa/cpuprobe.c log diff annotate
message retire NexGen CPU identification code

On OpenBSD/i386 we only support Pentium compatible CPUs with an FPU.
The NexGen CPUs probably don't meet this requirement so remove the
small amount of support code to identify this brand of CPU.

The Nx586 "P" models did not include an FPU as they were expected
to be paired with an Nx587 FPU (which was never officially released).

The Nx586 "FP" models did include an FPU, but even these are allegedly
386 clones and not Pentium compatible. According to some websites,
486 instructions were emulated via hypercode. However the 486
instruction emulation was only enough to run applications and wasn't
good enough to run an OS that needs newer 486 and Pentium instructions.

Finally, while our current code references the "Processor Recognition
Application Note", we only implement the half of the documented
algorithm to detect NexGen CPUs. We don't implement the second half
of the algorithm to check for the vendor string "NexGenDriven" on NexGen
CPUs that support the CPUID instruction (like the Nx586-P120 and Nx586-P133).

ok jsg@

date 2022-07-07T00:56:47Z
author daniel
files src/sys/arch/i386/stand/libsa/exec_i386.c log diff annotate
src/sys/arch/i386/stand/libsa/machdep.c log diff annotate
message retire NexGen CPU identification code

On OpenBSD/i386 we only support Pentium compatible CPUs with an FPU.
The NexGen CPUs probably don't meet this requirement so remove the
small amount of support code to identify this brand of CPU.

The Nx586 "P" models did not include an FPU as they were expected
to be paired with an Nx587 FPU (which was never officially released).

The Nx586 "FP" models did include an FPU, but even these are allegedly
386 clones and not Pentium compatible. According to some websites,
486 instructions were emulated via hypercode. However the 486
instruction emulation was only enough to run applications and wasn't
good enough to run an OS that needs newer 486 and Pentium instructions.

Finally, while our current code references the "Processor Recognition
Application Note", we only implement the half of the documented
algorithm to detect NexGen CPUs. We don't implement the second half
of the algorithm to check for the vendor string "NexGenDriven" on NexGen
CPUs that support the CPUID instruction (like the Nx586-P120 and Nx586-P133).

ok jsg@

date 2022-07-07T07:48:45Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
message remove a DPRINTF() from iwm(4) which no longer makes any sense

The conditions under which this debug message should trigger were
changed in r1.330 (cvs commit RcatFKLXoHUopLvW), which removed a
txd_done() call located before txq_advance(). The mbuf for the
most recently completed frame will no longer be NULL on entry.

Prompted by a question from waddlesplash at haiku-os.

date 2022-07-07T13:52:20Z
author mpi
files src/sys/uvm/uvm_vnode.c log diff annotate
message Revert previous attempt at serializing `uo_refs'.

It is incorrect to look at/modify `uo_refs' without lock in uvm_vnp_sync().
However sleeping is not possible and spinning introduces a deadlock with the
KERNEL_LOCK() when another thread faults on a mmaped region related to a
vnode we're currently synching.

A proper fix should be investigated. For now a kown a race, mostly safe due
to the KERNEL_LOCK(), is better than a possible deadlock.

Issue reported by caspar@

Discussed with and ok semarie@

date 2022-07-07T23:23:10Z
author jsg
files src/sys/dev/pci/drm/amd/amdgpu/amdgpu_irq.c log diff annotate
message Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"

From Alex Deucher
990132bebcc81aa95c1a1ac4422b0364753d9d39 in linux 5.15.y/5.15.53
a775e4e4941bf2f326aa36c58f67bd6c96cac717 in mainline linux

date 2022-07-07T23:23:11Z
author jsg
files src/sys/dev/pci/drm/amd/display/amdgpu_dm/amdgpu_dm.c log diff annotate
message Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"

From Alex Deucher
990132bebcc81aa95c1a1ac4422b0364753d9d39 in linux 5.15.y/5.15.53
a775e4e4941bf2f326aa36c58f67bd6c96cac717 in mainline linux

date 2022-07-07T23:25:48Z
author jsg
files src/sys/dev/pci/drm/amd/amdgpu/amdgpu_amdkfd.c log diff annotate
message drm/amdgpu: To flush tlb for MMHUB of RAVEN series

From Ruili Ji
31c371b61d13dd457fdcc27cd728c04ee09f9cdb in linux 5.15.y/5.15.53
5cb0e3fb2c54eabfb3f932a1574bff1774946bc0 in mainline linux

date 2022-07-07T23:28:58Z
author jsg
files src/sys/dev/pci/drm/i915/gem/i915_gem_context.c log diff annotate
message drm/i915/gem: add missing else

From katrinzhou
a13ea254268c5538f4c2f1a1a344ad07cd7b87d3 in linux 5.15.y/5.15.53
9efdd519d001ee3e761f6ff80d5eb123387421c1 in mainline linux

date 2022-07-07T23:32:11Z
author jsg
files src/sys/dev/pci/drm/include/uapi/drm/drm_fourcc.h log diff annotate
message drm/fourcc: fix integer type usage in uapi header

From Carlos Llamas
5b458d3de9cfac4a21b704c90c8c7eff244c8b13 in linux 5.15.y/5.15.53
20b8264394b33adb1640a485a62a84bc1388b6a3 in mainline linux