|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0 |
|
| #
1b3f88bc |
| 28-May-2024 |
Zhenlei Huang <[email protected]> |
linux(4): Add const qualifier to the value parameter of function handle_string()
The content that `value` point to is not going to be altered by function handle_string().
MFC after: 1 week
(cherry
linux(4): Add const qualifier to the value parameter of function handle_string()
The content that `value` point to is not going to be altered by function handle_string().
MFC after: 1 week
(cherry picked from commit 68c890b4433d3655c7df91cc43f89f4d6a8b35e4)
show more ...
|
|
Revision tags: release/13.3.0, release/14.0.0 |
|
| #
3460fab5 |
| 18-Aug-2023 |
Dmitry Chagin <[email protected]> |
linux(4): Remove sys/cdefs.h inclusion where it's not needed due to 685dc743
|
| #
685dc743 |
| 16-Aug-2023 |
Warner Losh <[email protected]> |
sys: Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
| #
4d846d26 |
| 10-May-2023 |
Warner Losh <[email protected]> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
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
show more ...
|
|
Revision tags: release/13.2.0 |
|
| #
d8e53d94 |
| 14-Feb-2023 |
Dmitry Chagin <[email protected]> |
linux(4): Cleanup includes under compat/linux
Cleanup unneeded includes, sort the rest according to style(9). No functional changes.
MFC after: 2 weeks
|
| #
10d16789 |
| 12-Feb-2023 |
Dmitry Chagin <[email protected]> |
linux(4): Get rid of the opt_compat.h include.
Since e013e369 COMPAT_LINUX, COMPAT_LINUX32 build options are removed, so include of opt_compat.h is no more needed.
MFC after: 2 weeks
|
|
Revision tags: release/12.4.0, release/13.1.0 |
|
| #
93494e42 |
| 19-Apr-2022 |
Mateusz Guzik <[email protected]> |
linux: plug a set-but-not-used var
Sponsored by: Rubicon Communications, LLC ("Netgate")
|
|
Revision tags: release/12.3.0 |
|
| #
5e8caee2 |
| 05-May-2021 |
Edward Tomasz Napierala <[email protected]> |
linux: remove redundant SDT tracepoints
Remove all the 'entry' and 'return' probes; they clutter up the source and are redundant to FBT.
Reviewed By: dchagin Sponsored By: EPSRC Differential Revisi
linux: remove redundant SDT tracepoints
Remove all the 'entry' and 'return' probes; they clutter up the source and are redundant to FBT.
Reviewed By: dchagin Sponsored By: EPSRC Differential Revision: https://reviews.freebsd.org/D30040
show more ...
|
|
Revision tags: release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0 |
|
| #
9c42fa94 |
| 25-Jun-2018 |
Ed Maste <[email protected]> |
Quiet unused fn warning for linuxulator w/o legacy syscalls
Sponsored by: Turing Robotic Industries
|
|
Revision tags: release/11.2.0 |
|
| #
931e2a1a |
| 15-Jun-2018 |
Ed Maste <[email protected]> |
linuxulator: do not include legacy syscalls on arm64
Existing linuxulator platforms (i386, amd64) support legacy syscalls, such as non-*at ones like open, but arm64 and other new platforms do not.
linuxulator: do not include legacy syscalls on arm64
Existing linuxulator platforms (i386, amd64) support legacy syscalls, such as non-*at ones like open, but arm64 and other new platforms do not.
Wrap these in #ifdef LINUX_LEGACY_SYSCALLS, #defined in the MD linux.h files. We may need finer grained control in the future but this is sufficient for now.
Reviewed by: andrew Sponsored by: Turing Robotic Industries Differential Revision: https://reviews.freebsd.org/D15237
show more ...
|
| #
0ba1b365 |
| 16-Feb-2018 |
Ed Maste <[email protected]> |
Rationalize license text on Linuxolator files
Many licenses on Linuxolator files contained small variations from the standard FreeBSD license text. To avoid license proliferation switch to the stan
Rationalize license text on Linuxolator files
Many licenses on Linuxolator files contained small variations from the standard FreeBSD license text. To avoid license proliferation switch to the standard 2-clause FreeBSD license for those files where I have permission from each of the listed copyright holders. Additional files waiting on permission from others are listed in review D14210.
Approved by: kan, marcel, sos, rdivacky MFC after: 1 week Sponsored by: The FreeBSD Foundation
show more ...
|
| #
7f2d13d6 |
| 27-Nov-2017 |
Pedro F. Giffuni <[email protected]> |
sys/compat: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - er
sys/compat: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0 |
|
| #
e0d3ea8c |
| 24-May-2015 |
Dmitry Chagin <[email protected]> |
Where possible we will use M_LINUX malloc(9) type. Move M_FUTEX defines to the linux_common.ko.
Differential Revision: https://reviews.freebsd.org/D1077 Reviewed by: emaste
|
|
Revision tags: release/10.1.0, release/9.3.0, release/10.0.0 |
|
| #
54366c0b |
| 25-Nov-2013 |
Attilio Rao <[email protected]> |
- For kernel compiled only with KDTRACE_HOOKS and not any lock debugging option, unbreak the lock tracing release semantic by embedding calls to LOCKSTAT_PROFILE_RELEASE_LOCK() direclty in the in
- For kernel compiled only with KDTRACE_HOOKS and not any lock debugging option, unbreak the lock tracing release semantic by embedding calls to LOCKSTAT_PROFILE_RELEASE_LOCK() direclty in the inlined version of the releasing functions for mutex, rwlock and sxlock. Failing to do so skips the lockstat_probe_func invokation for unlocking. - As part of the LOCKSTAT support is inlined in mutex operation, for kernel compiled without lock debugging options, potentially every consumer must be compiled including opt_kdtrace.h. Fix this by moving KDTRACE_HOOKS into opt_global.h and remove the dependency by opt_kdtrace.h for all files, as now only KDTRACE_FRAMES is linked there and it is only used as a compile-time stub [0].
[0] immediately shows some new bug as DTRACE-derived support for debug in sfxge is broken and it was never really tested. As it was not including correctly opt_kdtrace.h before it was never enabled so it was kept broken for a while. Fix this by using a protection stub, leaving sfxge driver authors the responsibility for fixing it appropriately [1].
Sponsored by: EMC / Isilon storage division Discussed with: rstone [0] Reported by: rstone [1] Discussed with: philip
show more ...
|
|
Revision tags: release/9.2.0, release/8.4.0 |
|
| #
d825ce0a |
| 29-Jan-2013 |
John Baldwin <[email protected]> |
Reduce duplication between i386/linux/linux.h and amd64/linux32/linux.h by moving bits that are MI out into headers in compat/linux.
Reviewed by: Chagin Dmitry dmitry | gmail MFC after: 2 weeks
|
|
Revision tags: release/9.1.0 |
|
| #
19e252ba |
| 05-May-2012 |
Alexander Leidinger <[email protected]> |
- >500 static DTrace probes for the linuxulator - DTrace scripts to check for errors, performance, ... they serve mostly as examples of what you can do with the static probe;s with moderate load
- >500 static DTrace probes for the linuxulator - DTrace scripts to check for errors, performance, ... they serve mostly as examples of what you can do with the static probe;s with moderate load the scripts may be overwhelmed, excessive lock-tracing may influence program behavior (see the last design decission)
Design decissions: - use "linuxulator" as the provider for the native bitsize; add the bitsize for the non-native emulation (e.g. "linuxuator32" on amd64) - Add probes only for locks which are acquired in one function and released in another function. Locks which are aquired and released in the same function should be easy to pair in the code, inter-function locking is more easy to verify in DTrace. - Probes for locks should be fired after locking and before releasing to prevent races (to provide data/function stability in DTrace, see the man-page of "dtrace -v ..." and the corresponding DTrace docs).
show more ...
|
|
Revision tags: release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0 |
|
| #
aefce619 |
| 19-Mar-2006 |
Ruslan Ermilov <[email protected]> |
Unbreak COMPAT_LINUX32 option support on amd64.
Broken by: netchild
|
| #
d4a3f5dd |
| 18-Mar-2006 |
Alexander Leidinger <[email protected]> |
Fixup some problems in my previous commit (COMPAT_43).
Pointyhat to: netchild
|
| #
5c8919ad |
| 18-Mar-2006 |
Alexander Leidinger <[email protected]> |
Get rid of the need of COMPAT_43 in the linuxolator.
Submitted by: Divacky Roman <[email protected]> Obtained from: DragonFly (some parts)
|
|
Revision tags: release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
| #
1997c537 |
| 14-Jan-2005 |
David E. O'Brien <[email protected]> |
Match the LINUX32's style with existing style Submitted by: Jung-uk Kim <[email protected]>
Use positive, not negative logic.
|
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
| #
4af27623 |
| 16-Aug-2004 |
Tim J. Robbins <[email protected]> |
Changes to MI Linux emulation code necessary to run 32-bit Linux binaries on AMD64, and the general case where the emulated platform has different size pointers than we use natively: - declare certai
Changes to MI Linux emulation code necessary to run 32-bit Linux binaries on AMD64, and the general case where the emulated platform has different size pointers than we use natively: - declare certain structure members as l_uintptr_t and use the new PTRIN and PTROUT macros to convert to and from native pointers. - declare some structures __packed on amd64 when the layout would differ from that used on i386. - include <machine/../linux32/linux.h> instead of <machine/../linux/linux.h> if compiling with COMPAT_LINUX32. This will need to be revisited before 32-bit and 64-bit Linux emulation support can coexist in the same kernel. - other small scattered changes.
This should be a no-op on i386 and Alpha.
show more ...
|
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0 |
|
| #
16dbc7f2 |
| 10-Jun-2003 |
David E. O'Brien <[email protected]> |
Use __FBSDID().
|
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0 |
|
| #
1d062e2b |
| 03-Mar-2003 |
Dag-Erling Smørgrav <[email protected]> |
Clean up whitespace and remove register keyword.
|
| #
4b7ef73d |
| 03-Mar-2003 |
Dag-Erling Smørgrav <[email protected]> |
More caddr_t removal, in conjunction with copy{in,out}(9) this time. Also clean up some egregious casts and incorrect use of sizeof.
|
| #
a163d034 |
| 19-Feb-2003 |
Warner Losh <[email protected]> |
Back out M_* changes, per decision of the TRB.
Approved by: trb
|