Link [ NetBSD | NetBSD OpenGrok source search | PR fulltext-search | Summary of daily snapshot builds | history of daily build result | pkgsrc commit viewer ]


   
        usage: [branch:branch] [user:user] [path@revision] keyword [... [-excludekeyword [...]]] (e.g. branch:MAIN sys/arch/arm, if_wm.c@1.234 )




switch to index mode

recent branches: MAIN (51m)  netbsd-8 (6d)  netbsd-10 (6d)  netbsd-9 (12d)  thorpej-ifq (176d)  thorpej-altq-separation (178d) 

2024-05-10 21:28:22 UTC Now

2023-07-31 14:42:46 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1860):

sys/kern/kern_rwlock.c: revision 1.67
sys/kern/kern_lock.c: revision 1.182
sys/kern/kern_mutex.c: revision 1.102
(all via patch)

Sprinkle __predict_{true,false} for panicstr checks

(martin)

2023-07-31 14:40:04 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1677):

sys/kern/kern_rwlock.c: revision 1.67
sys/kern/kern_lock.c: revision 1.182
sys/kern/kern_mutex.c: revision 1.102

Sprinkle __predict_{true,false} for panicstr checks

(martin)

2023-07-31 14:38:25 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #265):

sys/kern/kern_rwlock.c: revision 1.67
sys/kern/kern_lock.c: revision 1.182
sys/kern/kern_mutex.c: revision 1.102

Sprinkle __predict_{true,false} for panicstr checks

(martin)

2023-07-31 14:26:26 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1859):

sys/arch/ia64/ia64/vm_machdep.c: revision 1.18
sys/arch/powerpc/powerpc/locore_subr.S: revision 1.67
sys/arch/aarch64/aarch64/locore.S: revision 1.91
sys/arch/mips/include/asm.h: revision 1.74
sys/arch/hppa/include/cpu.h: revision 1.13
sys/arch/arm/arm/armv6_start.S: revision 1.38
(applied also to sys/arch/arm/cortex/a9_mpsubr.S,
sys/arch/arm/cortex/a9_mpsubr.S,
sys/arch/arm/cortex/cortex_init.S)
sys/arch/evbmips/ingenic/cpu_startup.S: revision 1.2
sys/arch/mips/mips/locore.S: revision 1.229
sys/arch/alpha/include/asm.h: revision 1.45
(applied to sys/arch/alpha/alpha/multiproc.s)
sys/arch/sparc64/sparc64/locore.s: revision 1.432
sys/arch/vax/vax/subr.S: revision 1.42
sys/arch/mips/mips/locore_mips3.S: revision 1.116
sys/arch/ia64/ia64/machdep.c: revision 1.44
sys/arch/arm/arm32/cpuswitch.S: revision 1.106
sys/arch/sparc/sparc/locore.s: revision 1.284
(all via patch)

aarch64: Add missing barriers in cpu_switchto.
Details in comments.

Note: This is a conservative change that inserts a barrier where
there was a comment saying none is needed, which is probably correct.
The goal of this change is to systematically add barriers to be
confident in correctness; subsequent changes may remove some bariers,
as an optimization, with an explanation of why each barrier is not
needed.

PR kern/57240

alpha: Add missing barriers in cpu_switchto.
Details in comments.

arm32: Add missing barriers in cpu_switchto.
Details in comments.

hppa: Add missing barriers in cpu_switchto.
Not sure hppa has ever had working MULTIPROCESSOR, so maybe no
pullups needed?

ia64: Add missing barriers in cpu_switchto.
(ia64 has never really worked, so no pullups needed, right?)

mips: Add missing barriers in cpu_switchto.
Details in comments.

powerpc: Add missing barriers in cpu_switchto.
Details in comments.

sparc: Add missing barriers in cpu_switchto.

sparc64: Add missing barriers in cpu_switchto.
Details in comments.

vax: Note where cpu_switchto needs barriers.

Not sure vax has ever had working MULTIPROCESSOR, though, and I'm not
even sure how to spell store-before-load barriers on VAX, so no
functional change for now.

(martin)

2023-07-31 13:56:15 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1859):

sys/arch/ia64/ia64/vm_machdep.c: revision 1.18
sys/arch/powerpc/powerpc/locore_subr.S: revision 1.67
sys/arch/aarch64/aarch64/locore.S: revision 1.91
sys/arch/mips/include/asm.h: revision 1.74
sys/arch/hppa/include/cpu.h: revision 1.13
sys/arch/arm/arm/armv6_start.S: revision 1.38
(applied also to sys/arch/arm/cortex/a9_mpsubr.S,
sys/arch/arm/cortex/a9_mpsubr.S,
sys/arch/arm/cortex/cortex_init.S)
sys/arch/evbmips/ingenic/cpu_startup.S: revision 1.2
sys/arch/mips/mips/locore.S: revision 1.229
sys/arch/alpha/include/asm.h: revision 1.45
(applied to sys/arch/alpha/alpha/multiproc.s)
sys/arch/sparc64/sparc64/locore.s: revision 1.432
sys/arch/vax/vax/subr.S: revision 1.42
sys/arch/mips/mips/locore_mips3.S: revision 1.116
sys/arch/ia64/ia64/machdep.c: revision 1.44
sys/arch/arm/arm32/cpuswitch.S: revision 1.106
sys/arch/sparc/sparc/locore.s: revision 1.284
(all via patch)

aarch64: Add missing barriers in cpu_switchto.
Details in comments.

Note: This is a conservative change that inserts a barrier where
there was a comment saying none is needed, which is probably correct.
The goal of this change is to systematically add barriers to be
confident in correctness; subsequent changes may remove some bariers,
as an optimization, with an explanation of why each barrier is not
needed.

PR kern/57240

alpha: Add missing barriers in cpu_switchto.
Details in comments.

arm32: Add missing barriers in cpu_switchto.
Details in comments.

hppa: Add missing barriers in cpu_switchto.
Not sure hppa has ever had working MULTIPROCESSOR, so maybe no
pullups needed?

ia64: Add missing barriers in cpu_switchto.
(ia64 has never really worked, so no pullups needed, right?)

mips: Add missing barriers in cpu_switchto.
Details in comments.

powerpc: Add missing barriers in cpu_switchto.
Details in comments.

sparc: Add missing barriers in cpu_switchto.

sparc64: Add missing barriers in cpu_switchto.
Details in comments.

vax: Note where cpu_switchto needs barriers.

Not sure vax has ever had working MULTIPROCESSOR, though, and I'm not
even sure how to spell store-before-load barriers on VAX, so no
functional change for now.

(martin)

2023-07-31 13:44:17 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #1676):

sys/arch/ia64/ia64/vm_machdep.c: revision 1.18
sys/arch/powerpc/powerpc/locore_subr.S: revision 1.67
sys/arch/aarch64/aarch64/locore.S: revision 1.91
sys/arch/mips/include/asm.h: revision 1.74
sys/arch/hppa/include/cpu.h: revision 1.13
sys/arch/arm/arm/armv6_start.S: revision 1.38
sys/arch/evbmips/ingenic/cpu_startup.S: revision 1.2
sys/arch/mips/mips/locore.S: revision 1.229
sys/arch/aarch64/aarch64/cpuswitch.S: revision 1.40
sys/arch/alpha/include/asm.h: revision 1.45
sys/arch/sparc64/sparc64/locore.s: revision 1.432
sys/arch/vax/vax/subr.S: revision 1.42
sys/arch/mips/mips/locore_mips3.S: revision 1.116
sys/arch/ia64/ia64/machdep.c: revision 1.44
sys/arch/arm/arm32/cpuswitch.S: revision 1.106
sys/arch/sparc/sparc/locore.s: revision 1.284
(all via patch)

aarch64: Add missing barriers in cpu_switchto.
Details in comments.

Note: This is a conservative change that inserts a barrier where
there was a comment saying none is needed, which is probably correct.
The goal of this change is to systematically add barriers to be
confident in correctness; subsequent changes may remove some bariers,
as an optimization, with an explanation of why each barrier is not
needed.

PR kern/57240

alpha: Add missing barriers in cpu_switchto.
Details in comments.

arm32: Add missing barriers in cpu_switchto.
Details in comments.

hppa: Add missing barriers in cpu_switchto.
Not sure hppa has ever had working MULTIPROCESSOR, so maybe no
pullups needed?

ia64: Add missing barriers in cpu_switchto.
(ia64 has never really worked, so no pullups needed, right?)

mips: Add missing barriers in cpu_switchto.
Details in comments.

powerpc: Add missing barriers in cpu_switchto.
Details in comments.

sparc: Add missing barriers in cpu_switchto.

sparc64: Add missing barriers in cpu_switchto.
Details in comments.

vax: Note where cpu_switchto needs barriers.

Not sure vax has ever had working MULTIPROCESSOR, though, and I'm not
even sure how to spell store-before-load barriers on VAX, so no
functional change for now.

(martin)

2023-07-31 13:36:32 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #264):

sys/arch/ia64/ia64/vm_machdep.c: revision 1.18
sys/arch/powerpc/powerpc/locore_subr.S: revision 1.67
sys/arch/aarch64/aarch64/locore.S: revision 1.91
sys/arch/mips/include/asm.h: revision 1.74
sys/arch/hppa/include/cpu.h: revision 1.13
sys/arch/arm/arm/armv6_start.S: revision 1.38
sys/arch/evbmips/ingenic/cpu_startup.S: revision 1.2
sys/arch/mips/mips/locore.S: revision 1.229
sys/arch/aarch64/aarch64/cpuswitch.S: revision 1.40
sys/arch/alpha/include/asm.h: revision 1.45
sys/arch/sparc64/sparc64/locore.s: revision 1.432
sys/arch/vax/vax/subr.S: revision 1.42
sys/arch/mips/mips/locore_mips3.S: revision 1.116
sys/arch/riscv/riscv/cpu_switch.S: revision 1.3
sys/arch/ia64/ia64/machdep.c: revision 1.44
sys/arch/arm/arm32/cpuswitch.S: revision 1.106
sys/arch/sparc/sparc/locore.s: revision 1.284

aarch64: Add missing barriers in cpu_switchto.
Details in comments.

Note: This is a conservative change that inserts a barrier where
there was a comment saying none is needed, which is probably correct.
The goal of this change is to systematically add barriers to be
confident in correctness; subsequent changes may remove some bariers,
as an optimization, with an explanation of why each barrier is not
needed.

PR kern/57240

alpha: Add missing barriers in cpu_switchto.
Details in comments.

arm32: Add missing barriers in cpu_switchto.
Details in comments.

hppa: Add missing barriers in cpu_switchto.
Not sure hppa has ever had working MULTIPROCESSOR, so maybe no
pullups needed?

ia64: Add missing barriers in cpu_switchto.
(ia64 has never really worked, so no pullups needed, right?)

mips: Add missing barriers in cpu_switchto.
Details in comments.

powerpc: Add missing barriers in cpu_switchto.
Details in comments.

riscv: Add missing barriers in cpu_switchto.
Details in comments.

sparc: Add missing barriers in cpu_switchto.

sparc64: Add missing barriers in cpu_switchto.
Details in comments.

vax: Note where cpu_switchto needs barriers.

Not sure vax has ever had working MULTIPROCESSOR, though, and I'm not
even sure how to spell store-before-load barriers on VAX, so no
functional change for now.

(martin)

2023-07-31 11:24:33 UTC MAIN commitmail json YAML

ahcisata: ASM106x needs EXTRA_DELAY quirk

(tnn)

2023-07-31 11:20:33 UTC MAIN commitmail json YAML

2023-07-31 11:18:20 UTC MAIN commitmail json YAML

pcidevs: add ASMedia ASM106x

(tnn)

2023-07-31 10:09:44 UTC MAIN commitmail json YAML

some updates:
- most platforms native-gcc works
- some platforms libgcc works
- amd64 kernels work
- i386 kernels build
- add info about libsanitizer re-port (all no.)

(mrg)

2023-07-31 10:07:42 UTC MAIN commitmail json YAML

src/external/gpl3/gcc/lib/libbacktrace/arch/aarch64/backtrace-supported.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libbacktrace/arch/aarch64/config.h@1.4 / diff / nxr@1.4
src/external/gpl3/gcc/lib/libbacktrace/arch/aarch64eb/backtrace-supported.h@1.4 / diff / nxr@1.4
src/external/gpl3/gcc/lib/libbacktrace/arch/aarch64eb/config.h@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/lib/libbacktrace/arch/alpha/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/alpha/config.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libbacktrace/arch/earm/backtrace-supported.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libbacktrace/arch/earm/config.h@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libbacktrace/arch/earmeb/backtrace-supported.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libbacktrace/arch/earmeb/config.h@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libbacktrace/arch/earmhf/backtrace-supported.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libbacktrace/arch/earmhf/config.h@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libbacktrace/arch/earmhfeb/backtrace-supported.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libbacktrace/arch/earmhfeb/config.h@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6/config.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6eb/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6eb/config.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6hf/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/earmv6hf/config.h@1.6 / diff / nxr@1.6
      :
(more 758 files)
mknative-gcc for GCC 12.3.0 on arm64*, arm* besides armv4, ppc, alpha,
sh, sparc*, mips*, riscv*, vax, hppa, ia64, and m68*.

earmv4 didn't start properly, and powerpc64 failed to build, but all
the rest seem to be OK now.

(mrg)

2023-07-31 05:36:41 UTC MAIN commitmail json YAML

web2: restore snit, accidentally lost in -r1.49

(dholland)

2023-07-31 05:35:44 UTC MAIN commitmail json YAML

web2: since we seem to be accumulating personal names in here, add a bunch.

(dholland)

2023-07-31 04:59:47 UTC MAIN commitmail json YAML

dw2c_fdt: Terminate statements by ; instead of , (from Mori Hiroki)
No binary changes.

(rin)

2023-07-31 04:46:22 UTC MAIN commitmail json YAML

2023-07-31 04:37:04 UTC MAIN commitmail json YAML

librump*: Require 10.99.7 or higher for __kevent100

(rin)

2023-07-31 02:38:16 UTC MAIN commitmail json YAML

when cpus are paused (spinning) in DDB, call x86_pause() in the loop,
hopefully this can reduce power usage while doing nothing.

ok chs@

XXX: pullup-*
XXX: apply to i386

(mrg)

2023-07-31 02:06:11 UTC MAIN commitmail json YAML

src/external/gpl3/gcc/lib/libbacktrace/arch/i386/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/i386/config.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libbacktrace/arch/x86_64/backtrace-supported.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libbacktrace/arch/x86_64/config.h@1.6 / diff / nxr@1.6
src/external/gpl3/gcc/lib/libgcc/arch/i386/auto-target.h@1.8 / diff / nxr@1.8
src/external/gpl3/gcc/lib/libgcc/arch/i386/defs.mk@1.15 / diff / nxr@1.15
src/external/gpl3/gcc/lib/libgcc/arch/x86_64/auto-target.h@1.8 / diff / nxr@1.8
src/external/gpl3/gcc/lib/libgcc/arch/x86_64/defs.mk@1.14 / diff / nxr@1.14
src/external/gpl3/gcc/lib/libgcc/libgcov/arch/i386/defs.mk@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libgcc/libgcov/arch/x86_64/defs.mk@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/lib/libgomp/arch/i386/config.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libgomp/arch/i386/libgomp_f.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libgomp/arch/i386/omp.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libgomp/arch/x86_64/config.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libgomp/arch/x86_64/libgomp_f.h@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libgomp/arch/x86_64/omp.h@1.10 / diff / nxr@1.10
src/external/gpl3/gcc/lib/libobjc/arch/i386/defs.mk@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libobjc/arch/x86_64/defs.mk@1.9 / diff / nxr@1.9
src/external/gpl3/gcc/lib/libstdc++-v3/arch/i386/c++config.h@1.38 / diff / nxr@1.38
src/external/gpl3/gcc/lib/libstdc++-v3/arch/i386/cxxabi_tweaks.h@1.9 / diff / nxr@1.9
      :
(more 28 files)
mknative-gcc for GCC 12.3.0 on amd64 and i386.

(mrg)

2023-07-31 01:48:37 UTC MAIN commitmail json YAML

updates for GCC 12 (relatively tiny).

- gcov-iov.h is now called version.h and we build it directly.
- need to explicitly ask for bversion.h gtyp-input.list to be built.

(mrg)

2023-07-31 01:46:59 UTC MAIN commitmail json YAML

add missing void to function prototype (not C++ here.)

(mrg)

2023-07-31 01:46:32 UTC MAIN commitmail json YAML

compiler include dir is gcc-12 here.

(mrg)

2023-07-31 01:46:04 UTC MAIN commitmail json YAML

2023-07-31 01:44:58 UTC MAIN commitmail json YAML

src/external/gpl3/gcc/dist/libsanitizer/asan/asan_activation.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_activation.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_activation.h@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_activation_flags.inc@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_allocator.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_allocator.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_allocator.h@1.7 / diff / nxr@1.7
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_debugging.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_debugging.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_descriptions.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_descriptions.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_descriptions.h@1.4 / diff / nxr@1.4
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_errors.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_errors.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_errors.h@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_fake_stack.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_fake_stack.cpp@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_fake_stack.h@1.3 / diff / nxr@1.3
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_flags.cc deleted
src/external/gpl3/gcc/dist/libsanitizer/asan/asan_flags.cpp@1.3 / diff / nxr@1.3
      :
(more 465 files)
make this actually be GCC 12.3.0's libsanitizer.

the libsanitizer we used with GCC 9 and GCC 10 was significantly
ahead of the GCC 9 and GCC 10 provided versions.

(mrg)

2023-07-31 01:24:36 UTC MAIN commitmail json YAML

aarp.c: one more thing -- both macro params should get parens

(dholland)

2023-07-31 01:23:04 UTC MAIN commitmail json YAML

aarp.c: whitespace

(dholland)

2023-07-31 01:19:50 UTC MAIN commitmail json YAML

aarp.c: fix wrong indent and add missing braces inside macro

(dholland)

2023-07-30 22:38:10 UTC MAIN commitmail json YAML

lint: increase debug logging for declarations, constify

Lint doesn't parse declarators correctly, see msg_347.c, and fixing this
part is nontrivial.

(rillig)

2023-07-30 22:27:21 UTC MAIN commitmail json YAML

lint: in debug mode, default to indenting the debug log

Only the 'parsing' lines are not indented, as line breaks are
independent from the structure of the code.

(rillig)

2023-07-30 20:34:45 UTC MAIN commitmail json YAML

bump for struct kevent changes.

(christos)

2023-07-30 20:12:35 UTC MAIN commitmail json YAML

lint: remove outdated comment (since decl.c 1.6 from 1995-10-02)

(rillig)

2023-07-30 19:03:50 UTC MAIN commitmail json YAML

Update build instruction for Solaris 11.4 (CBE) hosts

(palle)

2023-07-30 18:31:14 UTC MAIN commitmail json YAML

2023-07-30 12:39:18 UTC MAIN commitmail json YAML

timecounter(9): Nix trailing whitespace.

No functional change intended.

(riastradh)

2023-07-30 12:17:02 UTC MAIN commitmail json YAML

PR//57518: usb keyboard causes host controller to miss microframe

As per the USB 2.0 specification section 11.18.4; paragraph 3.b

For interrupt IN/OUT full-/low-speed transactions, the host must schedule a
complete-split transaction in each of the two microframes following the first
microframe in which the full-/low-speed transaction is budgeted. An additional
complete-split must also be scheduled in the third following microframe unless
the full-/low-speed transaction was budgeted to start in microframe Y6.

(skrll)

2023-07-30 12:16:28 UTC netbsd-8 commitmail json YAML

2023-07-30 12:15:40 UTC netbsd-9 commitmail json YAML

2023-07-30 12:15:04 UTC netbsd-10 commitmail json YAML

2023-07-30 12:13:02 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #263):

share/man/man9/pcq.9: revision 1.9
sys/kern/subr_pcq.c: revision 1.14
sys/kern/subr_pcq.c: revision 1.15
sys/kern/subr_pcq.c: revision 1.16
sys/kern/subr_pcq.c: revision 1.17
sys/kern/subr_pcq.c: revision 1.18
sys/kern/subr_pcq.c: revision 1.19

pcq(9): Make pcq_put a release operation, in memory ordering.

Otherwise, for example, the following assertion could fail:
        /* publisher */
        nusers = foo->nusers;
        pcq_put(pcq, foo);
        KASSERT(nusers == 0);
        /* user */
        foo = pcq_get(pcq);
        if (foo != NULL)
                atomic_inc_uint(&foo->nusers);

pcq(9): Fix consume operation in pcq_peek/get.

These use atomic_load_consume to match the atomic_store_release in
pcq_put for pcq->pcq_items[c].

Reading the snapshot of pcq->pcq_pc need not be ordered:
- The consumer side (pcq_peek/get) is serialized by the API contract
  (single-consumer, multi-producer), so no ordering is necessary.
- The producer side updates pcq->pcq_pc first; if the consumer side
  sees that before the producer side has stored pcq->pcq_items[c],
  there's no problem -- it's as if the consumer had happened just a
  moment earlier and the producer hadn't entered pcq_put yet.

However, it should be an atomic load, not a plain load.  So use
atomic_load_relaxed, if for no other reason than to pacify thread
sanitizers.

pcq(9): Explain why store need not be atomic in pcq_get.
No functional change intended.

pcq(9): Explain why membar_release isn't needed in pcq_get.
No functional change intended.

pcq(9): Document memory ordering guarantees.

pcq(9): Sketch correctness proof for some critical properties.
No functional change intended.

pcq(9): KASSERT(A && B) -> KASSERT(A); KASSERT(B)

(martin)

2023-07-30 12:09:51 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #262):

sys/kern/kern_descrip.c: revision 1.252
sys/kern/kern_descrip.c: revision 1.253
sys/kern/kern_descrip.c: revision 1.254

kern_descrip.c: Fix membars around reference count decrement.

In general, the `last one out hit the lights' style of reference
counting (as opposed to the `whoever's destroying must wait for
pending users to finish' style) requires memory barriers like so:
        ... usage of resources associated with object ...
        membar_release();
        if (atomic_dec_uint_nv(&obj->refcnt) != 0)
                return;
        membar_acquire();
        ... freeing of resources associated with object ...

This way, all usage happens-before all freeing.  This fixes several
errors:
- fd_close failed to ensure whatever its caller did would
  happen-before the freeing, in the case where another thread is
  concurrently trying to close the fd (ff->ff_file == NULL).
  Fix: Add membar_release before atomic_dec_uint(&ff->ff_refcnt) in
  that branch.
- fd_close failed to ensure all loads its caller had issued will have
  happened-before the freeing, in the case where the fd is still in
  use by another thread (fdp->fd_refcnt > 1 and ff->ff_refcnt-- > 0).
  Fix: Change membar_producer to membar_release before
  atomic_dec_uint(&ff->ff_refcnt).
- fd_close failed to ensure that any usage of fp by other callers
  would happen-before any freeing it does.
  Fix: Add membar_acquire after atomic_dec_uint_nv(&ff->ff_refcnt).
- fd_free failed to ensure that any usage of fdp by other callers
  would happen-before any freeing it does.
  Fix: Add membar_acquire after atomic_dec_uint_nv(&fdp->fd_refcnt).

While here, change membar_exit -> membar_release.  No semantic
change, just updating away from the legacy API.

kern_descrip.c: Use atomic_store_relaxed/release for ff->ff_file.
1. atomic_store_relaxed in fd_close avoids the appearance of race in
  sanitizers (minor bug).
2. atomic_store_release in fd_affix is necessary because the lock
  activity was not, in fact, enough to guarantee ordering (real bug
  some architectures like aarch64).
  The premise appears to have been that the mutex_enter/exit earlier
  in fd_affix is enough to guarantee that initialization of fp (A)
  happens before use of fp by a user once fp is published (B):
        fp->f_... = ...;                // A
        /* fd_affix */
        mutex_enter(&fp->f_lock);
        fp->f_count++;
        mutex_exit(&fp->f_lock);
        ...
        ff->ff_file = fp;              // B
  But actually mutex_enter/exit allow the following reordering by
  the CPU:
        mutex_enter(&fp->f_lock);
        ff->ff_file = fp;              // B
        fp->f_count++;
        fp->f_... = ...;                // A
        mutex_exit(&fp->f_lock);
  The only constraints they imply are:
        1. fp->f_count++ and B cannot precede mutex_enter
        2. mutex_exit cannot precede A and fp->f_count++
  They imply no constraint on the relative ordering of A, B, and
  fp->f_count++ amongst each other, however.
  This affects any architecture that has a native load-acquire or
  store-release operation in mutex_enter/exit, like aarch64, instead
  of explicit load-before-load/store and load/store-before-store
  barrier.

No need for atomic_store_* in fd_copy or fd_free because we have
exclusive access to ff as is.

kern_descrip.c: Change membar_enter to membar_acquire in fd_getfile.
membar_acquire is cheaper on many CPUs, and unlikely to be costlier
on any CPUs, than the legacy membar_enter.
Add a long comment explaining the interaction between fd_getfile and
fd_close and why membar_acquire is safe.

(martin)

2023-07-30 12:06:55 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by mrg in ticket #261):

share/mk/bsd.x11.mk: revision 1.147

properly prefix ${X11INCDIR} uses with ${DESTDIR}.

this fixes a build issue seen where the host pixman.h was included,
and has been problem ever since tsutsui fixed my original code (from
2008) about 29 months ago.  i'm surprised this has not been seen
anywhere else in that time.

(martin)

2023-07-30 12:04:22 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #260):

sys/kern/subr_autoconf.c: revision 1.314

autoconf(9): Print `waiting for devices' normally once a minute.

(martin)

2023-07-30 12:01:54 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by riastradh in ticket #259):

sys/dev/acpi/acpi_ec.c: revision 1.102
sys/dev/acpi/acpi_ec.c: revision 1.103
sys/dev/acpi/acpi_ec.c: revision 1.104
sys/dev/acpi/acpi_ec.c: revision 1.105
sys/dev/acpi/acpi_ec.c: revision 1.106
sys/dev/acpi/acpi_ec.c: revision 1.107
sys/dev/acpi/acpi_ec.c: revision 1.108
sys/dev/acpi/acpi_ec.c: revision 1.90
sys/dev/acpi/acpi_ec.c: revision 1.91
sys/dev/acpi/acpi_ec.c: revision 1.92
sys/dev/acpi/acpi_ec.c: revision 1.93
sys/dev/acpi/acpi_ec.c: revision 1.94
sys/dev/acpi/files.acpi: revision 1.128
sys/dev/acpi/acpi_ec.c: revision 1.95
sys/dev/acpi/acpi_ec.c: revision 1.96
sys/dev/acpi/acpi_ec.c: revision 1.97
sys/arch/amd64/conf/ALL: revision 1.179
sys/dev/acpi/acpi_ec.c: revision 1.98
sys/dev/acpi/acpi_ec.c: revision 1.99
sys/dev/acpi/acpi_ec.c: revision 1.87
sys/dev/acpi/acpi_ec.c: revision 1.88
sys/dev/acpi/acpi_ec.c: revision 1.89
sys/arch/i386/conf/ALL: revision 1.511
sys/dev/acpi/acpi_ec.c: revision 1.100
sys/dev/acpi/acpi_ec.c: revision 1.101

acpiec(4): Record device_t self.

Not used yet, to be used soon for device_printf and to allow making
some of the internal functions a little more type-safe later.
acpiec(4): New ACPIEC_DEBUG option.

Value is bit mask of debug messages to enable.

Enable in x86/ALL kernels.

No functional change intended when the option is off.

acpiec(4): Clarify lock order and sprinkle lock assertions.
No functional change intended.

acpiec(4): Sprinkle comments.
Note where this code is abusing cv_wait and needs a loop to handle
spurious wakeups.
No functional change intended.

acpiec(4): Assert state is free when we start a transaction.
No functional change intended.

acpiec(4): Set sc_got_sci only when a transaction is over.

Before, when the acpiec thread noticed an SCI had been requested and
entered acpiec_gpe_state_machine to send the query command, it would
see the SCI is still requested -- because it had yet to acknowledge
it by setting the query command! -- and think the EC was asking for a
_second_ SCI.

So once the first SCI transaction was over, it would start a second
one, even though the EC hadn't asked for another -- and this would
wedge on some ECs.

Now, acpiec_gpe_state_machine waits to see what state we transition
to before taking the SCI bit to mean we need to notify the acpiec
thread to handle another query.

That way, when the acpiec thread enters acpiec_gpe_state_machine with
EC_STATE_QUERY, it can send the query command first, with the side
effect of clearing the SCI bit in subsequent reads of the status
register, and it won't think another SCI has been requested until it
returns to EC_STATE_FREE and sees the SCI bit set again in the status
register.

Possibly relevant PRs:
PR kern/53135
PR kern/52763
PR kern/57162

acpiec(4): Fix cv_wait loop around sc->sc_got_sci.

That is, make it actually loop as required, so it gracefully handles
spurious wakeups instead of barging into invalid states.

acpiec(4): Fix interrupt wait loop in acpiec_gpe_query thread.

acpiec(4): Fix cv_timedwait abuse in acpiec_read/write.

acpiec(4): Don't touch sc->sc_state outside sc->sc_mtx.

acpiec(4): Merge returns in acpiec_read/write.
No functional change intended.

acpiec(4): Factor wait logic out.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_gpe_state_machine.
Simpler, type-safer.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_callout.
Simpler.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_gpe_handler.
Simpler.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_lock/unlock.
Simpler, type-safer.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_read/write.
Simpler, type-safer.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_gpe_query thread.
Simpler.
No functional change intended.

acpiec(4): Pass softc, not device_t, to acpiec_space_handler.
Better to keep the device_t isolated to public interfaces.  Simpler
internally this way.
No functional change intended.

acpiec(4): Factor out if (state == FREE) cv_signal(sc_cv).

In principle this could have a functional change, but at worst, it is
to signal more wakeups than needed, which should always be safe.
acpiec(4): Take a lock around acpiec_cold updates.

Otherwise we race with readers -- probably harmlessly, but let's
avoid the appearance of problems.
XXX Maybe acpiec_suspend and acpiec_shutdown should interrupt
transactions and force them to fail promptly?
XXX This looks bad because acpiec_cold is global and sc->sc_mtx
doesn't look like it's global, but we expect to have only one
acpiec(4) device anyway from what I understand.  Maybe we should move
acpiec_cold into the softc?

acpiec(4): One more debug message about read/write polling timeout.

(martin)

2023-07-30 11:53:39 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by rin in ticket #1858):

lib/csu/arch/vax/crtbegin.S: revision 1.8
lib/csu/arch/vax/crtbegin.S: revision 1.9

vax/csu: __do_global_ctors_aux: Save actually-used r8, instead of r11

Thanks Kalvis Duckmanton for report and patch on tech-toolchain:
https://mail-index.netbsd.org/tech-toolchain/2023/07/28/msg004321.html

vax/csu: Use register name provided by asm.h. No binary changes.

(martin)

2023-07-30 11:52:02 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by rin in ticket #1675):

lib/csu/arch/vax/crtbegin.S: revision 1.8
lib/csu/arch/vax/crtbegin.S: revision 1.9

vax/csu: __do_global_ctors_aux: Save actually-used r8, instead of r11

Thanks Kalvis Duckmanton for report and patch on tech-toolchain:
https://mail-index.netbsd.org/tech-toolchain/2023/07/28/msg004321.html

vax/csu: Use register name provided by asm.h. No binary changes.

(martin)

2023-07-30 11:50:28 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by rin in ticket #258):

lib/csu/arch/vax/crtbegin.S: revision 1.8
lib/csu/arch/vax/crtbegin.S: revision 1.9

vax/csu: __do_global_ctors_aux: Save actually-used r8, instead of r11

Thanks Kalvis Duckmanton for report and patch on tech-toolchain:
https://mail-index.netbsd.org/tech-toolchain/2023/07/28/msg004321.html

vax/csu: Use register name provided by asm.h. No binary changes.

(martin)

2023-07-30 11:47:08 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by uwe in ticket #257):
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.25
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.26
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.27
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.28
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.29
sys/dev/wscons/wsemul_vt100.c: revision 1.50
sys/dev/wscons/wsemul_vt100.c: revision 1.51
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.30
sys/dev/wscons/wsemul_vt100_subr.c: revision 1.31

Fix off by one (Crystal Kolipe in tech-kern@)

Add rin, indn, vpa, hpa, and cbt terminfo capabilities (Crystal Kolipe)

wscons(4): Ignore nonsense tab stops in vt100 emulation.

wscons(4): Paranoia: Clamp numbers of rows and columns.

wsemul_vt100_subr: don't assert unsigned ncols >= 0

wsemul_vt100_subr: spell edp->tabs assertion with NULL

Avoid overflow with too many ';' (David Leadbeater)

Prefix all messages with the method name

wsemul_vt100_subr: complete the refactoring from 2010
In 1.20 refactoring, functions in this file were changed to accept a
pointer to the new base class instead of the full emuldata:
  -wsemul_vt100_foo(struct wsemul_vt100_emuldata *edp, ...)
  +wsemul_vt100_foo(struct vt100base_data *edp, ...)
but the argument name was not changed.  While this saved on the diff
churn back then, it created a rather unfortunate situation where the
same emulation state variables are referred to differently in this
file and other vt100 emulation files.  Complete that old change by
renaming the base class arguments to match the variable name used for
it in other files.

Same object code is generated.

(martin)

2023-07-30 11:41:48 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by gutteridge in ticket #256):

sys/arch/mips/cavium/dev/octeon_rnm.c: revision 1.16 (patch)

octrnm(4): Raise delay on startup.

According to CN50XX-HRM-V0.99E and CN78XX-HM-0.99E:
    The entropy is provided by the jitter of 125 of 128 free-running
    oscillators XORed into a 128-bit LFSR.  The LFSR accumulates entropy
    over 81 cycles, after which it is fed into a SHA-1 engine.
    [...]
    The SHA-1 engine runs once every 81 cycles.
    [...]
    The hardware produces new 64-bit random number every 81 cycles.

The last sentence means that we only need to wait 81 cycles _between_
consecutive SHA-1 outputs (which isn't relevant anyway because we
reconfigure it into raw mode later), but the first two quotes might
mean that we need to wait 81+81 cycles for the _first_ output to be
produced on boot when running the self-test.

Now, in this case, the self-test is run with the LFSR unhooked, by
clearing the RNM_CTL_STATUS[ENT_EN] bit, so that SHA-1 is computed
from a known input -- this is really just paranoia to make sure that
_some_ functions of the device (which is conjured out of thin air at
a fixed virtual address, with no firmware bindings to guide us)
behave as we expect.

And it's not clear if it really does take 81+81 cycles for the first
SHA-1 output to appear when the LFSR isn't feeding into it anyway.

But experimentally, delay of 81+81 cycles seems to work whereas a
delay of only 81 cycles crashes.
PR kern/57280

(martin)

2023-07-30 11:39:33 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by gutteridge in ticket #256):

sys/arch/mips/cavium/dev/octeon_rnm.c: revision 1.16

octrnm(4): Raise delay on startup.

According to CN50XX-HRM-V0.99E and CN78XX-HM-0.99E:
    The entropy is provided by the jitter of 125 of 128 free-running
    oscillators XORed into a 128-bit LFSR.  The LFSR accumulates entropy
    over 81 cycles, after which it is fed into a SHA-1 engine.
    [...]
    The SHA-1 engine runs once every 81 cycles.
    [...]
    The hardware produces new 64-bit random number every 81 cycles.

The last sentence means that we only need to wait 81 cycles _between_
consecutive SHA-1 outputs (which isn't relevant anyway because we
reconfigure it into raw mode later), but the first two quotes might
mean that we need to wait 81+81 cycles for the _first_ output to be
produced on boot when running the self-test.

Now, in this case, the self-test is run with the LFSR unhooked, by
clearing the RNM_CTL_STATUS[ENT_EN] bit, so that SHA-1 is computed
from a known input -- this is really just paranoia to make sure that
_some_ functions of the device (which is conjured out of thin air at
a fixed virtual address, with no firmware bindings to guide us)
behave as we expect.

And it's not clear if it really does take 81+81 cycles for the first
SHA-1 output to appear when the LFSR isn't feeding into it anyway.

But experimentally, delay of 81+81 cycles seems to work whereas a
delay of only 81 cycles crashes.
PR kern/57280

(martin)

2023-07-30 10:45:11 UTC MAIN commitmail json YAML

wsmouse(4): Make wsmouse_input safe to call from MP-safe interrupts.

XXX pullup-10

(riastradh)

2023-07-30 09:23:22 UTC MAIN commitmail json YAML

hack(6): Fix a segfault that occurs when ASLR is enabled

Prior to this change, savenames() would store "objects" in save files as a
blob, and restnames() would load it and overwrite "objects". But since
objclass::oc_name and oc_descr are pointers to string constants, they would
be invalid when the next time the process is spawned, and opening the
inventory would crash by dereferencing invalid pointers.

(pho)

2023-07-30 09:22:02 UTC MAIN commitmail json YAML

ld.elf_so: Add some known-answer tests for hash functions.

Make sure the testing mechanism detects the traditional overflow bug.

(riastradh)

2023-07-30 09:20:14 UTC MAIN commitmail json YAML

2023-07-30 09:19:19 UTC MAIN commitmail json YAML

ld.elf_so: Sort SRCS.

No functional change intended.

(riastradh)

2023-07-30 09:19:10 UTC MAIN commitmail json YAML

ld.elf_so: Split SRCS onto multiple lines.

Makes updates easier.

No functional change intended.

(riastradh)

2023-07-30 09:09:38 UTC MAIN commitmail json YAML

Resolve the port 2049 conflict by commenting out the entries for "shilp".
Now "netstat" will produce sensible output for NFS connections again.

(tron)

2023-07-30 08:58:54 UTC MAIN commitmail json YAML

lint: in memory debug mode, log the type of the nodes

First log all objects to be freed, then free them all at once.  This
allows cross references from the objects of a block independent of their
allocation order.

(rillig)

2023-07-30 07:56:15 UTC MAIN commitmail json YAML

netbsd32_epoll_pwait2: Dedup slightly. NFCI.

(rin)

2023-07-30 07:48:54 UTC MAIN commitmail json YAML

netbsd32_epoll_pwait2: Early return if no event arrived;
Do not attempt to allocate 0-byte buffer by kmem_alloc(9).

(rin)

2023-07-30 06:53:13 UTC MAIN commitmail json YAML

2023-07-30 06:52:21 UTC MAIN commitmail json YAML

2023-07-30 06:37:23 UTC MAIN commitmail json YAML

update for GCC 12.

amd64 tools already work.  everything else is unknown.

(mrg)

2023-07-30 06:36:21 UTC MAIN commitmail json YAML

mark our GCC 12 as "nb1 20230729".

(mrg)

2023-07-30 06:24:25 UTC MAIN commitmail json YAML

2023-07-30 06:15:17 UTC MAIN commitmail json YAML

src/external/gpl3/gcc/dist/gcc/c-family/c-cppbuiltin.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/c-family/c-format.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/c-family/c-opts.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/cfgexpand.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/common/config/aarch64/aarch64-common.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/common/config/arm/arm-common.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/aarch64/aarch64-builtins.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/aarch64/driver-aarch64.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/host-darwin.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/i386/i386.h@1.17 / diff / nxr@1.17
src/external/gpl3/gcc/dist/gcc/config/i386/netbsd-elf.h@1.17 / diff / nxr@1.17
src/external/gpl3/gcc/dist/gcc/config/i386/netbsd64.h@1.17 / diff / nxr@1.17
src/external/gpl3/gcc/dist/gcc/config/mips/mips.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/pa/pa.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/rs6000/rs6000-logue.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/config/rs6000/rs6000.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/cppbuiltin.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/cppdefault.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/dse.cc@1.2 / diff / nxr@1.2
src/external/gpl3/gcc/dist/gcc/expr.cc@1.2 / diff / nxr@1.2
      :
(more 15 files)
GCC 12.3.0: merge our old changes into the renamed .cc files.

(mrg)

2023-07-30 05:51:45 UTC MAIN commitmail json YAML

initial merge of GCC 12.3.0.

this doesn't include any of the changes to the .c -> .cc files renamed,
and reverts our local changes to the vax port and libsanitizer subdir.
vax GCC was rewritten and our local fixes no longer are relevant, and
the new libsanitizer is more updated than our old one, and merging via
gcc10->gcc12 is not really possible.

unfortunately, our local changes to libsanitizer that aren't related
to the general update of those sources (ie, the netbsd code) will need
to be re-checked and perhaps re-ported.

(mrg)

2023-07-30 05:31:30 UTC MAIN commitmail json YAML

2023-07-30 05:30:45 UTC MAIN commitmail json YAML

2023-07-30 05:10:48 UTC MAIN commitmail json YAML

netbsd32_netbsd: Sort headers. No binary changes.

(rin)

2023-07-30 04:39:00 UTC MAIN commitmail json YAML

sys_epoll: whitespace -> tab. no binary changes.

(rin)

2023-07-30 00:11:32 UTC MAIN commitmail json YAML

New sentence, new line.

(wiz)

2023-07-29 23:59:59 UTC MAIN commitmail json YAML

sys_memfd: Comply with our implicit naming convention;
do_memfd_truncate() --> memfd_truncate_locked(). NFC.

(rin)

2023-07-29 23:51:29 UTC MAIN commitmail json YAML

sys_memfd: Fix logic errors for offset in the previous.

(rin)

2023-07-29 23:50:03 UTC MAIN commitmail json YAML

drm/linux_ww_mutex: Fix ww acquire context ordering.

XXX pullup-8
XXX pullup-9
XXX pullup-10

(riastradh)

2023-07-29 23:11:51 UTC MAIN commitmail json YAML

nvmm(4): Document that VMX Unrestricted Guest is required

(gdt)

2023-07-29 22:43:56 UTC MAIN commitmail json YAML

drm/linux_ww_mutex: Fix wait loops.

If cv_wait_sig returns because a signal is delivered, we may
nonetheless have been granted the lock.  It is harmless for us to
ignore this fact in three of the four paths, but in
ww_mutex_state_wait_sig, we may now have ownership of the lock and
MUST NOT return failure because the caller MUST release the lock
before destroying the ww_acquire_ctx.

While here, restructure the other three loops for clarity, so they
match the structure of the fourth and so they have a little less
impenetrable negation.

PR kern/57537

XXX pullup-8
XXX pullup-9
XXX pullup-10

(riastradh)

2023-07-29 17:54:54 UTC MAIN commitmail json YAML

Fix locking and offset issues pointed out by @riastradh (Theodore Preduta)

(christos)

2023-07-29 17:33:51 UTC MAIN commitmail json YAML

ews4800mips/floppies: Fix ramdisk overflow by dropping IEEE 802.11
support from x_ifconfig

(rin)

2023-07-29 16:47:28 UTC MAIN commitmail json YAML

CHANGES: remove entry that has been pulled up to netbsd-10

(gutteridge)

2023-07-29 16:24:36 UTC MAIN commitmail json YAML

t_memfd_create: Fix printf-like format by using %zu for size_t, and
%jd for off_t with cast to intmax_t, respectively.

(rin)

2023-07-29 15:46:45 UTC MAIN commitmail json YAML

No need to ask whether to use the TCP option on NFS mount.

TCP mount has been default since NetBSD 9.0.

(tsutsui)

2023-07-29 15:11:04 UTC MAIN commitmail json YAML

rump: Regen again to fix missing __kevent100 symbol.

makerumpsyscalls.sh requires rebuilt rump libraries installed in
/usr/lib or directory specified by its first argument.

Now, new failures observed for ATF after __kevent100 addition are
fixed at least for aarch64.

(rin)

2023-07-29 15:05:46 UTC MAIN commitmail json YAML

2023-07-29 15:05:31 UTC MAIN commitmail json YAML

2023-07-29 15:04:29 UTC MAIN commitmail json YAML

2023-07-29 14:54:02 UTC MAIN commitmail json YAML

sys/memfd.h: Fix include guards after rename.

(riastradh)

2023-07-29 13:57:28 UTC MAIN commitmail json YAML

2023-07-29 13:40:51 UTC MAIN commitmail json YAML

COMPAT_NETBSD32: Reorganize the previous; Make compat_netbsd32_50 recursively
depended on compat_netbsd32_100, rather than directly depended on it.

Thanks pgoyette@ again for useful comments!

(rin)

2023-07-29 13:13:50 UTC MAIN commitmail json YAML

Now, netbsd32_compat_50 module requires netbsd32_compat_100.
Thanks pgoyette@ for hints.

(rin)

2023-07-29 12:58:51 UTC MAIN commitmail json YAML

Add comment on packed attribution for struct linux_epoll_event on amd64.
NFC.

(rin)

2023-07-29 12:48:15 UTC MAIN commitmail json YAML

2023-07-29 12:39:20 UTC MAIN commitmail json YAML

2023-07-29 12:38:25 UTC MAIN commitmail json YAML

2023-07-29 12:16:34 UTC MAIN commitmail json YAML

2023-07-29 11:58:53 UTC MAIN commitmail json YAML

Sprinkle __inline to compat_100___kevent50_{fetch_changes,put_events}

(rin)

2023-07-29 11:48:37 UTC netbsd-8 commitmail json YAML

2023-07-29 11:44:09 UTC netbsd-9 commitmail json YAML

2023-07-29 11:42:32 UTC netbsd-10 commitmail json YAML

2023-07-29 11:07:17 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #255):

usr.sbin/tprof/arch/tprof_x86.c: revision 1.18
usr.sbin/tprof/arch/tprof_x86.c: revision 1.19

Modify comment. No functional change.

tprof(8): Add support for Skylake-X and Cascade Lake.

(martin)

2023-07-29 11:03:21 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #1857):

sys/arch/x86/x86/coretemp.c: revision 1.38-1.39 (patch)

coretemp(4): Change limits of Tjmax.
- Change the lower limit from 70 to 60. At least, some BIOSes can change
  the value down to 62.
- Change the upper limit from 110 to 120. At least, some BIOSes can change
  the value up to 115.
- Print error message when rdmsr(TEMPERATURE_TARGET) failed.
- When Tjmax exceeded the limit, print warning message and use the value
  as it is.
- KNF.

(martin)

2023-07-29 11:03:19 UTC MAIN commitmail json YAML

lint: eliminate redundant code

No functional change.

(rillig)

2023-07-29 11:01:15 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #254):

sys/arch/x86/x86/coretemp.c: revision 1.38-1.39 (patch)

coretemp(4): Change limits of Tjmax.
- Change the lower limit from 70 to 60. At least, some BIOSes can change
  the value down to 62.
- Change the upper limit from 110 to 120. At least, some BIOSes can change
  the value up to 115.
- Print error message when rdmsr(TEMPERATURE_TARGET) failed.
- When Tjmax exceeded the limit, print warning message and use the value
  as it is.
- KNF.

(martin)

2023-07-29 10:58:02 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by msaitoh in ticket #254):

sys/arch/x86/x86/coretemp.c: revision 1.39

coretemp(4): Change limits of Tjmax.
- Change the lower limit from 70 to 60. At least, some BIOSes can change
  the value down to 62.
- Change the upper limit from 110 to 120. At least, some BIOSes can change
  the value up to 115.
- Print error message when rdmsr(TEMPERATURE_TARGET) failed.
- When Tjmax exceeded the limit, print warning message and use the value
  as it is.

(martin)

2023-07-29 10:54:05 UTC netbsd-8 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #1856:

sys/dev/pci/ichsmb.c 1.83-1.84

- Add support Intel 700 series chipset and Alder Lake-N devices.
- Use device_printf() instead of aprint_error_dev() in
  ichsmb_i2c_exec().

(martin)

2023-07-29 10:52:20 UTC netbsd-9 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #1672:

sys/dev/pci/ichsmb.c 1.83-1.84

- Add support Intel 700 series chipset and Alder Lake-N devices.
- Use device_printf() instead of aprint_error_dev() in
  ichsmb_i2c_exec().

(martin)

2023-07-29 10:50:05 UTC netbsd-10 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #253:

sys/dev/pci/ichsmb.c 1.83-1.84

- Add support Intel 700 series chipset and Alder Lake-N devices.
- Use device_printf() instead of aprint_error_dev() in
  ichsmb_i2c_exec().

(martin)

2023-07-29 10:45:00 UTC MAIN commitmail json YAML

lint1: remove option -m

The list of lint messages is only needed for generating the manual page
lint.7.  Since 2022-07-06, that list is extracted from the source code
instead of compiling and then running lint1.

(rillig)

2023-07-29 10:44:35 UTC netbsd-8 commitmail json YAML

2023-07-29 10:42:40 UTC netbsd-8 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #1855:

sys/dev/pci/pcidevs                            1.1481-1.1482

Add Intel Alder Lake-N, Raptor Lake and 700 series chipset devices.

(martin)

2023-07-29 10:34:24 UTC MAIN commitmail json YAML

2023-07-29 10:32:07 UTC netbsd-9 commitmail json YAML

2023-07-29 10:30:37 UTC netbsd-9 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #1671:

sys/dev/pci/pcidevs                            1.1481-1.1482

Add Intel Alder Lake-N, Raptor Lake and 700 series chipset devices.

(martin)

2023-07-29 10:27:38 UTC netbsd-10 commitmail json YAML

2023-07-29 10:26:20 UTC netbsd-10 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh
in ticket #252:

sys/dev/pci/pcidevs                            1.1481-1.1482

Add Intel Alder Lake-N, Raptor Lake and 700 series chipset devices.

(martin)

2023-07-29 10:23:07 UTC netbsd-8 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh
in ticket #1854:

usr.sbin/cpuctl/arch/i386.c                    1.137-1.139

- CPU model 0x5a is not Atom E3500 but Atom Z3500.
- Add Alder Lake-N.

(martin)

2023-07-29 10:22:50 UTC MAIN commitmail json YAML

lint: fix use-after-free in memory debug mode

A node may be allocated before its type.  Since the objects are freed in
reverse allocation order, the type cannot be accessed anymore when the
node is freed.

(rillig)

2023-07-29 10:14:09 UTC netbsd-9 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh
in ticket #1670:

usr.sbin/cpuctl/arch/i386.c                    1.137-1.139

- CPU model 0x5a is not Atom E3500 but Atom Z3500.
- Add Alder Lake-N.

(martin)

2023-07-29 10:07:59 UTC netbsd-10 commitmail json YAML

Pull up the following revisions, via patch, requested by msaitoh in
ticket #251:

usr.sbin/cpuctl/arch/i386.c                    1.137-1.139

- CPU model 0x5a is not Atom E3500 but Atom Z3500.
- Add Alder Lake-N.

(martin)

2023-07-29 10:01:24 UTC MAIN commitmail json YAML

libc: Warn of __kevent50 when itself (not kevent) is referenced

(rin)

2023-07-29 09:51:56 UTC netbsd-8 commitmail json YAML

Pull up the following revisions, all via patch, requested by msaitoh
in ticket #1853:

sys/arch/x86/include/specialreg.h 1.204-1.206, 1.208

- Add Intel CPUID 0x07 %ecx bit 24 BUS_LOCK_DETECT.
- Add AMD CPUID 0x80000008 %ebx bit 30 IBPB_RET and CPUID 0x8000000a
  %edx bit 29 BusLockThreshold.
- Fix typo in comment.

(martin)

2023-07-29 09:48:51 UTC netbsd-9 commitmail json YAML

Pull up the following revisions, all via patch, requested by msaitoh
in ticket #1669:

sys/arch/x86/include/specialreg.h              1.204-1.206, 1.208

- Add Intel CPUID 0x07 %ecx bit 24 BUS_LOCK_DETECT.
- Add AMD CPUID 0x80000008 %ebx bit 30 IBPB_RET and CPUID 0x8000000a
  %edx bit 29 BusLockThreshold.
- Fix typo in comment.

(martin)

2023-07-29 09:44:34 UTC netbsd-10 commitmail json YAML

Pull up the following revisions, all via patch, requested by msaitoh
in ticket #250:

sys/arch/x86/include/specialreg.h              1.204-1.206, 1.208

- Add Intel CPUID 0x07 %ecx bit 24 BUS_LOCK_DETECT.
- Add AMD CPUID 0x80000008 %ebx bit 30 IBPB_RET and CPUID 0x8000000a
  %edx bit 29 BusLockThreshold.
- Fix typo in comment.

(martin)

2023-07-29 08:46:58 UTC MAIN commitmail json YAML

sys/memfd.h: Tidy.

- Sort includes.
- #include <sys/types.h> for size_t.

(riastradh)

2023-07-29 08:46:47 UTC MAIN commitmail json YAML

sys: Rename sys/miscfd.h -> sys/memfd.h.

Let's not create new dumping grounds for miscellaneous stuff; one
header file for one purpose.

(riastradh)

2023-07-29 08:46:27 UTC MAIN commitmail json YAML

memfd(2): Convert KASSERT to CTASSERT.

Move it closer to where it's relevant too.

(riastradh)

2023-07-29 07:49:15 UTC MAIN commitmail json YAML

2023-07-29 07:26:53 UTC MAIN commitmail json YAML

2023-07-29 07:03:19 UTC MAIN commitmail json YAML

lint: remove forward declarations for functions

No functional change.

(rillig)

2023-07-29 07:00:00 UTC MAIN commitmail json YAML

compat/linux: aarch64 does not have epoll_create(2) nor epoll_wait(2)

Note that for Linux, new architectures like arm64 use MI system call
table in include/uapi/asm-generic/unistd.h, instead of MD syscall.tbl.

XXX
Too many ifdef's like this. We should be smarter...

(rin)

2023-07-29 06:59:47 UTC MAIN commitmail json YAML

Slight reformatting. NFCI.

(skrll)

2023-07-29 06:50:47 UTC MAIN commitmail json YAML

2023-07-29 06:47:26 UTC MAIN commitmail json YAML

linux/aarch64/syscalls.master: Dedup and sort headers. NFC.

(rin)

2023-07-29 06:45:50 UTC MAIN commitmail json YAML

linux/aarch64/syscalls.master: Include linux_misc.h.

(rin)

2023-07-29 06:44:44 UTC MAIN commitmail json YAML

lint: use standard function attribute for noreturn functions

(rillig)

2023-07-29 04:06:32 UTC MAIN commitmail json YAML

remove extra `_' to fix debug build

(pgoyette)

2023-07-28 23:41:16 UTC MAIN commitmail json YAML

2023-07-28 23:41:02 UTC MAIN commitmail json YAML

Remove Pp that have no effect.

(wiz)

2023-07-28 22:05:44 UTC MAIN commitmail json YAML

2023-07-28 21:50:03 UTC MAIN commitmail json YAML

lint: extract 'vararg' and 'prototype' flags from global 'dcs'

These flags are only relevant for parameter lists, so add a separate
type for it.

No functional change.

(rillig)

2023-07-28 19:01:45 UTC MAIN commitmail json YAML

2023-07-28 19:01:11 UTC MAIN commitmail json YAML

2023-07-28 18:20:53 UTC MAIN commitmail json YAML

2023-07-28 18:20:29 UTC MAIN commitmail json YAML

2023-07-28 18:19:01 UTC MAIN commitmail json YAML

2023-07-28 14:27:35 UTC MAIN commitmail json YAML

Gcc complains about overflow writing 53 bytes into a region of size 35,
and it is correct for the alphabet copying line, which correctly comments
about the overflow too.

(christos)

2023-07-28 12:03:33 UTC MAIN commitmail json YAML

ostat: use standard option order (AaBb...)

Fix macro usage while here

(wiz)

2023-07-28 11:22:43 UTC MAIN commitmail json YAML

vax/csu: __start: Use 0x0000 as entry mask instead of 0x0101 (two NOPs)

This was a quite common trick to able to load executables with a.out
headers stripped. Now, the system boots successfully into multi-user
mode without this trick.

Thanks ragge@ for kind explanation:
https://mail-index.netbsd.org/port-vax/2023/07/28/msg004397.html

(rin)

2023-07-28 10:39:14 UTC MAIN commitmail json YAML

xen_clock(4): New hardclock dtrace probes.

sdt:xen:hardclock:tick(last, now)
  fires on every hardclock tick

sdt:xen:hardclock:jump(last, now, nticks)
  fires on every hardclock tick when (now - last) >= 2*NS_PER_TICK,
  i.e., this call to the timer interrupt handler requires multiple
  hardclock ticks

(riastradh)

2023-07-28 10:39:01 UTC MAIN commitmail json YAML

xen_clock(4): Compute NS_PER_TICK only once per call.

This involves a division by an unknown number, so let's cache it.

XXX Could do better by precomputing it in xen_resumeclocks, with some
effort to ensure concurrent calls don't stomp on each other.

(riastradh)

2023-07-28 10:38:44 UTC MAIN commitmail json YAML

xen_clock(4): Fix whitespace and sprinkle comments.

No functional change intended.

(riastradh)

2023-07-28 10:37:28 UTC MAIN commitmail json YAML

timecounter(9): Link to phk's timecounter paper for reference.

No functional change intended.

(riastradh)

2023-07-28 09:47:37 UTC MAIN commitmail json YAML

openssh: Apply __dead to print_config() to fix build with clang

(rin)

2023-07-28 09:18:59 UTC MAIN commitmail json YAML

add iostat -X option, limited alternative statistics.

this is like the "-D" option, except it skips the xfers/s, and
reports MB/s instead of KB/s.  allows for far more devices to
be displayed per line by default (about 50% more.)

(mrg)

2023-07-28 08:05:29 UTC MAIN commitmail json YAML

gcc 10 is now in gcc.old, make mknative-gcc.old gcc-10 happy.

(mrg)

2023-07-28 07:17:30 UTC MAIN commitmail json YAML

vax/csu: Use register name provided by asm.h. No binary changes.

(rin)

2023-07-28 07:04:41 UTC MAIN commitmail json YAML

vax/csu: __do_global_ctors_aux: Save actually-used r8, instead of r11

Thanks Kalvis Duckmanton for report and patch on tech-toolchain:
https://mail-index.netbsd.org/tech-toolchain/2023/07/28/msg004321.html

(rin)

2023-07-28 06:21:02 UTC MAIN commitmail json YAML

arm/bus_dma: Fix misleading comment:

- * For a virtually-indexed write-back cache, we need
- * to do the following things:
+ * For a write-back cache, we need to do the following things:

This comment was written long ago when we supported only virtually-
indexed caches for arm. But subsequent comments are valid also for
physically-indexed cache.

(rin)

2023-07-28 05:06:44 UTC MAIN commitmail json YAML

2023-07-28 05:02:47 UTC MAIN commitmail json YAML

openssh: KNF for our local changes.

(rin)

2023-07-28 05:02:13 UTC MAIN commitmail json YAML

x86: make the CPUID list for errata be far less confusing

the 0x80000001 CPUID result needs some parsing to match against
actual family/model/stepping values.  4-bit 'family' values of
15 or 6 change how to parse the 4-bit extended model and 8-bit
extended family value - for family 6 or 15, the extended model
bits (4) are concatenated with the base 4-bits to create an
8-bit value, and for family 15, the family value is addition
of the family value and the 8-bit extended-family value, giving
a range of 0 to 15 + 0xff aka 270.

use a CPUREV(family, model, stepping) macro that builds the
relevant bit-representation of a CPUID, making it far easier
to understand what each entry means, and to add new ones too.

i have confirmed that the emitted cpurevs[] array has the same
values before/after this change, ie, NFCI or observed.

(mrg)

2023-07-28 04:59:40 UTC MAIN commitmail json YAML

ssh_config.5: Change in comment from upstream.

(rin)

2023-07-28 04:58:27 UTC MAIN commitmail json YAML

2023-07-28 04:55:40 UTC MAIN commitmail json YAML

ssh-keygen.1: Catch up upstream change in comment.

(rin)

2023-07-28 04:52:23 UTC MAIN commitmail json YAML

2023-07-28 04:49:38 UTC MAIN commitmail json YAML

sftp.1: Fix old (and non-critical) merge botch.

(rin)

2023-07-28 04:40:54 UTC MAIN commitmail json YAML

openssh: Adjust blank line to reduce diff from upstream.

(rin)

2023-07-28 04:37:37 UTC MAIN commitmail json YAML

2023-07-28 04:27:30 UTC MAIN commitmail json YAML

2023-07-28 04:25:22 UTC MAIN commitmail json YAML

openssh: Reduce diff from upstream; remove never-enabled #if 0'ed block

(rin)

2023-07-28 03:57:35 UTC OPENSSH commitmail json YAML

2023-07-28 02:41:31 UTC MAIN commitmail json YAML

Simplify fix for PR toolchain/57146

Introduce ARCH_STRIP_SYMBOLS variable to centralize logic for debug
symbols from MD Makefile's to Makefile.kern.inc.

(rin)

2023-07-28 02:28:33 UTC MAIN commitmail json YAML

Add Zen4 Phoenix support.

(msaitoh)

2023-07-28 02:27:25 UTC MAIN commitmail json YAML

2023-07-28 02:26:58 UTC MAIN commitmail json YAML

Add AMD 19h/7xh Root Complex.

(msaitoh)

2023-07-28 02:05:26 UTC MAIN commitmail json YAML

Add Zen2 Mendocino APU support.

(msaitoh)

2023-07-28 00:11:15 UTC MAIN commitmail json YAML

Add Zen4 Ryzen "Phoenix" support.

(msaitoh)

2023-07-27 21:59:55 UTC MAIN commitmail json YAML

2023-07-27 21:59:29 UTC MAIN commitmail json YAML

CHANGES: fix a typo

(gutteridge)

2023-07-27 21:58:51 UTC MAIN commitmail json YAML

2023-07-27 18:12:07 UTC netbsd-8 commitmail json YAML

2023-07-27 18:11:16 UTC netbsd-9 commitmail json YAML

2023-07-27 18:10:25 UTC netbsd-10 commitmail json YAML

2023-07-27 18:01:37 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by gutteridge in ticket #249):

distrib/evbmips/instkernel/ramdisk/Makefile: revision 1.16
distrib/evbmips/instkernel/ramdisk/Makefile: revision 1.17
distrib/evbmips/instkernel/ramdisk/Makefile: revision 1.18
distrib/evbmips/instkernel/ramdisk/list: revision 1.19

Add bpf to the device nodes provided in the evbmips ramdisk

Intended to address an issue noted by Denis Ovsienko on port-mips,
where dhcpcd doesn't work with the netbsd-INSTALL_OCTEON kernel. (I am
not able to test this directly, but verified by mounting the ramdisk
images generated before and after this change.)

Remove redundant variable assignment
It got clobbered by another assignment later, and this has been the
case since r. 1.1 of the file.

Add dk[0-3] to the device nodes provided in the evbmips ramdisk
The installer provided by octeon.img creates wedges, which may later
need to be recovered via the standard sysinst installer provided by
netbsd-INSTALL_OCTEON.

Add dkctl(8) and gpt(8) to the evbmips ramdisk

The installer provided by octeon.img creates GPT wedges, which may
later need to be recovered via the standard sysinst installer provided
by netbsd-INSTALL_OCTEON.

(martin)

2023-07-27 17:56:31 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #248):

sys/arch/xen/xen/xbd_xenbus.c: revision 1.132 (patch)
sys/arch/xen/xen/xbd_xenbus.c: revision 1.133 (patch)
sys/arch/xen/xen/xbd_xenbus.c: revision 1.134 (patch)

The disk size reported in the xenstore is always in XEN_BSIZE units,
not sector-size. Should fix the issue reported by Christian Kujau
on netbsd-users and port-xen.

Also use XEN_BSIZE when computing the number of bytes for format_bytes().
While there note in a comment that sc_sectors is in XEN_BSIZE units

Propoerly handle 4k sector size backends:
- report the backend's sector size to upper layers, not DEV_BSIZE.
  Adjust the number of sectors accordingly.
- Use sc_secsize instead of XEN_BSIZE where appropriate. The sectors numbers
  in I/O requests are still in XEN_BSIZE units, but must be a multiple
  of sc_secsize/XEN_BSIZE.
- As a consequence of previous, the buffer has to be aligned to sc_secsize,
  aligned to XEN_BSIZE may not be enough. This means that we may have to
  xbd_map_align() more buffer, including some without B_PHYS set.
- Add some more DPRINTF lines, related to I/O requests

Tested with a linux dom0.

thanks to Christian Kujau for providing access to his hardware for testing
and debugging.

(martin)

2023-07-27 17:21:21 UTC MAIN commitmail json YAML

doc: clarify changes entry

(nia)

2023-07-27 16:57:11 UTC MAIN commitmail json YAML

doc: Changes for July

(nia)

2023-07-27 16:55:41 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by bouyer in ticket #1668):

sys/arch/xen/xen/xen_clock.c: revision 1.10
sys/arch/xen/xen/xen_clock.c: revision 1.12
(applied to sys/arch/xen/xen/clock.c)

Unmask event after VCPUOP_stop_periodic_timer and
initializing ci->ci_xen_hardclock_systime_ns, to avoid a possible race with
xen_timer_handler()

Unmask event after arming the one-shot timer in clock initialisation,
to avoid a possible race with xen_timer_handler() updating
ci_xen_hardclock_systime_ns while we're reading it.

Pointed out by Taylor R Campbell

(martin)

2023-07-27 16:42:04 UTC netbsd-8 commitmail json YAML

Pull up following revision(s) (requested by mrg in ticket #1852):

sys/arch/x86/x86/errata.c: revision 1.32

fix the cpuids for the zen2 client CPUs.

i'm not exactly how i came up with the values i had, though one
of them was still valid and matched my test systems.

(martin)

2023-07-27 16:40:50 UTC netbsd-9 commitmail json YAML

Pull up following revision(s) (requested by mrg in ticket #1667):

sys/arch/x86/x86/errata.c: revision 1.32

fix the cpuids for the zen2 client CPUs.

i'm not exactly how i came up with the values i had, though one
of them was still valid and matched my test systems.

(martin)

2023-07-27 16:39:41 UTC netbsd-10 commitmail json YAML

Pull up following revision(s) (requested by mrg in ticket #247):

sys/arch/x86/x86/errata.c: revision 1.32

fix the cpuids for the zen2 client CPUs.

i'm not exactly how i came up with the values i had, though one
of them was still valid and matched my test systems.

(martin)

2023-07-27 10:32:25 UTC MAIN commitmail json YAML

dhcpd: move isc_event_free() before isc_timer_destroy() in timer cb

isc_timerevent_destroy() called by isc_event_free() expects to be able to
hold the timer lock, so must run before the timer is destroyed.
PR misc/57491.

(tnn)

2023-07-27 08:44:42 UTC MAIN commitmail json YAML

include glyph name in -d output

(macallan)

2023-07-27 08:30:02 UTC MAIN commitmail json YAML

document command line option

(macallan)

2023-07-27 01:48:49 UTC MAIN commitmail json YAML

kern: Restore non-atomic time_second symbol.

This is used by savecore(8), vmstat(8), and possibly other things.

XXX Should really teach dump and savecore(8) to use an intentionally
designed header, rather than relying on kvm(3) -- and make it work
for saving cores from other kernels so you don't have to boot the
same buggy kernel to get a core dump.

(riastradh)

2023-07-27 00:34:07 UTC MAIN commitmail json YAML

Add AMD IBPB_RET and BusLockThreshold.

(msaitoh)

2023-07-26 21:45:29 UTC MAIN commitmail json YAML

x86/pmap: Print quantities in failed assertions in pmap_load.

(riastradh)

2023-07-26 18:00:51 UTC MAIN commitmail json YAML

2023-07-26 17:59:35 UTC MAIN commitmail json YAML

2023-07-26 17:58:16 UTC MAIN commitmail json YAML

Merge changes between OpenSSH-9.1 and OpenSSH-9.3

(christos)

2023-07-26 10:46:01 UTC MAIN commitmail json YAML

wsemul_vt100_subr: complete the refactoring from 2010

In 1.20 refactoring, functions in this file were changed to accept a
pointer to the new base class instead of the full emuldata:

  -wsemul_vt100_foo(struct wsemul_vt100_emuldata *edp, ...)
  +wsemul_vt100_foo(struct vt100base_data *edp, ...)

but the argument name was not changed.  While this saved on the diff
churn back then, it created a rather unfortunate situation where the
same emulation state variables are referred to differently in this
file and other vt100 emulation files.  Complete that old change by
renaming the base class arguments to match the variable name used for
it in other files.

Same object code is generated.

(uwe)