src/tools/uma, branch releng/14.3FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F14.32023-08-16T17:55:03ZRemove $FreeBSD$: one-line sh pattern2023-08-16T17:55:03ZWarner Loshimp@FreeBSD.org2023-08-16T17:55:03Zurn:sha1:d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Remove $FreeBSD$: two-line .h pattern2023-08-16T17:54:16ZWarner Loshimp@FreeBSD.org2023-08-16T17:54:16Zurn:sha1:b3e7694832e81d7a904a10f525f8797b753bf0d3
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD2023-05-12T16:44:03ZWarner Loshimp@FreeBSD.org2023-05-10T15:40:58Zurn:sha1:4d846d260e2b9a3d4d0a701462568268cbfe7a5b
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
tools/uma/smrstress: fix kthread exit2022-07-30T21:40:12ZKonstantin Belousovkib@FreeBSD.org2022-07-30T18:54:34Zurn:sha1:4690e20eed17a6e79a67a8d10874fdc67a1c4ccf
By convention, kernel threads must call kthread_exit() instead of
blindly returning from the thread function. We have some safety measure
in fork_exit(), which checks for the P_KPROC p_flag and does
kthread_exit() for kernel thread that forgot to do it itself.
But this workaround only works for kernel threads belonging to the
kernel process. If a kernel thread is attached to the normal process
with live userspace, and does not call kthread_exit(), then the
workaround is not activated, and for amd64 at least, the return from the
thread function/fork_exit() results in the return to userspace with the
copy of frame from the thread that did kthread_add().
Practically for smrstress, this destroys the user stack of the still
active frame in the other thread, which was the caller of kthread_add().
Fix it by adding kthread_exit() to the thread function.
Reported and tested by: pho
Reviewed by: markj
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D35999
Fix the smrstress build after r358400.2020-08-05T17:26:20ZMark Johnstonmarkj@FreeBSD.org2020-08-05T17:26:20Zurn:sha1:36cc9d5ca5041c1d0748c04bff0c71597827ec66
Reported by: pho
smrstress: Add 'publishing' fences to operations on smrs_current.2020-01-31T20:30:50ZKonstantin Belousovkib@FreeBSD.org2020-01-31T20:30:50Zurn:sha1:4b919d5cdd0bf2bdd518c9b5767cb9fad754bbc9
Reported and tested by: andrew
Reviewed by: jeff
Sponsored by: The FreeBSD Foundation
Differential revision: https://reviews.freebsd.org/D23440
Implement a simple UMA SMR stress testing tool.2020-01-31T02:18:56ZJeff Robersonjeff@FreeBSD.org2020-01-31T02:18:56Zurn:sha1:e14f729cdc2a320e9fde1c7c1a869d0920df6a0c