src/sys/cddl/contrib/opensolaris, branch main FreeBSD source tree cddl: remove sparc and mips code 2026-01-10T05:05:37+00:00 Minsoo Choo minsoochoo0122@proton.me 2025-12-01T15:10:06+00:00 c29ec2ee9871cc21c3406bf6ed398980acbedcb5 Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me> Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1910 
Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me>
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1910
mips: remove mips leftovers 2026-01-06T17:56:50+00:00 Minsoo Choo minsoochoo0122@proton.me 2025-12-01T02:48:05+00:00 6c6e00b7f16f3bda1b56da6a57d65ff6e26ae3e7 Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me> Pull-request: https://github.com/freebsd/freebsd-src/pull/1909 
Signed-off-by: Minsoo Choo <minsoochoo0122@proton.me>
Pull-request: https://github.com/freebsd/freebsd-src/pull/1909
zfs: fix build after openzfs/zfs@e63d026b9 2025-11-17T16:11:56+00:00 Martin Matuska mm@FreeBSD.org 2025-11-16T11:15:14+00:00 4303bde4297a3d19cabdb08ce1550f682578d2ba Fix Makefiles Update zfs_config.h and zfs_gitrev.h 
Fix Makefiles
Update zfs_config.h and zfs_gitrev.h
dtrace: Deduplicate dtrace_sync() and dtrace_xcall() implementations 2025-09-18T22:09:49+00:00 Mark Johnston markj@FreeBSD.org 2025-09-17T15:29:48+00:00 bf115203bb8a61bd03ba23931ff0b5bf931b7d1b dtrace_xcall() is just a thin wrapper around smp_rendezvous_cpus(). There's no need for six identical implementations to live in MD layers. No functional change intended. MFC after: 2 weeks 
dtrace_xcall() is just a thin wrapper around smp_rendezvous_cpus().
There's no need for six identical implementations to live in MD layers.

No functional change intended.

MFC after:	2 weeks
dtrace: Use a size_t to represent a buffer size in the printm action 2025-09-10T16:00:13+00:00 Mark Johnston markj@FreeBSD.org 2025-09-10T14:33:58+00:00 3877025f52ee205fe99ad4ff68229933d57e4bcb printm is specific to the FreeBSD dtrace port. I believe it's effectively the same as tracemem(), though printm apparently predates it. It stores the size of the buffer of traced data inline. Currently it represents that size using a uintptr_t, which isn't really right and poses challenges when porting to CHERI because `DTRACE_STORE(uintptr_t, ...` requires the destination to be suitably aligned, but this isn't necessary since we're just storing a size. Convert to using a size_t. This should be a no-op since sizeof(uintptr_t) == sizeof(size_t) on non-CHERI platforms (and besides that I don't see a reason to use printm() when tracemem() is available and is simpler to use.) Reviewed by: Domagoj Stolfa, avg MFC after: 2 weeks Sponsored by: Innovate UK Differential Revision: https://reviews.freebsd.org/D52055 
printm is specific to the FreeBSD dtrace port.  I believe it's
effectively the same as tracemem(), though printm apparently predates
it.  It stores the size of the buffer of traced data inline.  Currently
it represents that size using a uintptr_t, which isn't really right and
poses challenges when porting to CHERI because
`DTRACE_STORE(uintptr_t, ...`  requires the destination to be suitably
aligned, but this isn't necessary since we're just storing a size.

Convert to using a size_t.  This should be a no-op since
sizeof(uintptr_t) == sizeof(size_t) on non-CHERI platforms (and besides
that I don't see a reason to use printm() when tracemem() is available
and is simpler to use.)

Reviewed by:	Domagoj Stolfa, avg
MFC after:	2 weeks
Sponsored by:	Innovate UK
Differential Revision:	https://reviews.freebsd.org/D52055
dtrace: Add compiler barriers around updates to per-CPU flags 2025-05-28T21:05:16+00:00 Mark Johnston markj@FreeBSD.org 2025-05-28T20:45:27+00:00 0440b3d2cbf83afb55209a9938b31a48912f222c Otherwise there's nothing preventing reordering of memory accesses with respect to these flags being set or cleared. Since their most common use is to create a section in dtrace probe context where memory faults are intercepted by dtrace_trap(), such reordering can turn dtrace errors into fatal exceptions. MFC after: 2 weeks Sponsored by: Innovate UK 
Otherwise there's nothing preventing reordering of memory accesses with
respect to these flags being set or cleared.  Since their most common
use is to create a section in dtrace probe context where memory faults
are intercepted by dtrace_trap(), such reordering can turn dtrace errors
into fatal exceptions.

MFC after:	2 weeks
Sponsored by:	Innovate UK
dtrace: fix signature mismatch for taskqueue callbacks 2025-02-24T14:56:29+00:00 SHENGYI HONG aokblast@FreeBSD.org 2025-02-23T17:42:41+00:00 a1452eec4768272056aa070db94ea7184ce1117c Reviewed by: markj MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D49112 
Reviewed by:	markj
MFC after:	1 week
Differential Revision: https://reviews.freebsd.org/D49112
dtrace: Remove the noinline qualifier from dtrace_getarg() 2025-01-25T17:33:43+00:00 Mark Johnston markj@FreeBSD.org 2025-01-25T17:22:02+00:00 494a2b14722e8955af54e306305f462e5765c1e4 It serves no purpose after commit 82283cad12a4. No functional change intended. Fixes: 82283cad12a4 ("dtrace: Avoid including dtrace_isa.c directly into dtrace.c") MFC after: 2 weeks 
It serves no purpose after commit 82283cad12a4.  No functional change
intended.

Fixes:	82283cad12a4 ("dtrace: Avoid including dtrace_isa.c directly into dtrace.c")
MFC after:	2 weeks
dtrace: Use size_t instead of uintptr_t to represent buffer offsets 2025-01-23T19:08:46+00:00 Mark Johnston markj@FreeBSD.org 2025-01-23T19:08:46+00:00 ba9cff7aa2eb62d84bead503cd606d1586ea8388 This eases porting of DTrace to CHERI, where uintptr_t and size_t aren't interchangeable. No functional change intended. Reviewed by: Domagoj Stolfa <domagoj.stolfa@gmail.com> MFC after: 2 weeks Sponsored by: Innovate UK Differential Revision: https://reviews.freebsd.org/D48625 
This eases porting of DTrace to CHERI, where uintptr_t and size_t aren't
interchangeable.

No functional change intended.

Reviewed by:	Domagoj Stolfa <domagoj.stolfa@gmail.com>
MFC after:	2 weeks
Sponsored by:	Innovate UK
Differential Revision:	https://reviews.freebsd.org/D48625
dtrace: Fix the definition of pc_t 2025-01-22T14:40:50+00:00 Mark Johnston markj@FreeBSD.org 2025-01-22T14:34:29+00:00 8ce6b4f2c48eca758fac90b58924f9b2e38fbc49 This type is used only to store PC values corresponding to a thread stack trace, so a pointer type is not quite right. Switch to vm_offset_t, as in struct stack, to simplify a port of DTrace to CHERI. No functional change intended. MFC after: 1 week Sponsored by: Innovate UK 
This type is used only to store PC values corresponding to a thread
stack trace, so a pointer type is not quite right.  Switch to
vm_offset_t, as in struct stack, to simplify a port of DTrace to CHERI.

No functional change intended.

MFC after:	1 week
Sponsored by:	Innovate UK