Searched hist:1.175 (Results 1 - 25 of 326) sorted by relevance

1234567891011>>

/src/sys/arch/amiga/conf/
H A DDRACO1.175 Sat Jul 05 10:00:42 GMT 2014 tsutsui branches: 1.175.2; 1.175.4; 1.175.8;
Regen from GENERIC.in rev 1.125:

> Use COPTS="-O2 -fno-reorder-blocks" for kernels except INSTALL_CONFIGURATION.

1.175 Sat Jul 05 10:00:42 GMT 2014 tsutsui branches: 1.175.2; 1.175.4; 1.175.8;
Regen from GENERIC.in rev 1.125:

> Use COPTS="-O2 -fno-reorder-blocks" for kernels except INSTALL_CONFIGURATION.

1.175 Sat Jul 05 10:00:42 GMT 2014 tsutsui branches: 1.175.2; 1.175.4; 1.175.8;
Regen from GENERIC.in rev 1.125:

> Use COPTS="-O2 -fno-reorder-blocks" for kernels except INSTALL_CONFIGURATION.

1.175 Sat Jul 05 10:00:42 GMT 2014 tsutsui branches: 1.175.2; 1.175.4; 1.175.8;
Regen from GENERIC.in rev 1.125:

> Use COPTS="-O2 -fno-reorder-blocks" for kernels except INSTALL_CONFIGURATION.

/src/sys/arch/i386/conf/
H A DMakefile.i3861.175 Wed Sep 14 14:58:08 GMT 2011 christos branches: 1.175.2; 1.175.6;
include wakecode after so that the depend rules are defined!
1.175 Wed Sep 14 14:58:08 GMT 2011 christos branches: 1.175.2; 1.175.6;
include wakecode after so that the depend rules are defined!
1.175 Wed Sep 14 14:58:08 GMT 2011 christos branches: 1.175.2; 1.175.6;
include wakecode after so that the depend rules are defined!
/src/sys/arch/sparc/sparc/
H A Dtrap.c1.175 Thu Apr 24 18:39:21 GMT 2008 ad branches: 1.175.2; 1.175.4; 1.175.8;
Merge proc::p_mutex and proc::p_smutex into a single adaptive mutex, since
we no longer need to guard against access from hardware interrupt handlers.

Additionally, if cloning a process with CLONE_SIGHAND, arrange to have the
child process share the parent's lock so that signal state may be kept in
sync. Partially addresses PR kern/37437.

1.175 Thu Apr 24 18:39:21 GMT 2008 ad branches: 1.175.2; 1.175.4; 1.175.8;
Merge proc::p_mutex and proc::p_smutex into a single adaptive mutex, since
we no longer need to guard against access from hardware interrupt handlers.

Additionally, if cloning a process with CLONE_SIGHAND, arrange to have the
child process share the parent's lock so that signal state may be kept in
sync. Partially addresses PR kern/37437.

1.175 Thu Apr 24 18:39:21 GMT 2008 ad branches: 1.175.2; 1.175.4; 1.175.8;
Merge proc::p_mutex and proc::p_smutex into a single adaptive mutex, since
we no longer need to guard against access from hardware interrupt handlers.

Additionally, if cloning a process with CLONE_SIGHAND, arrange to have the
child process share the parent's lock so that signal state may be kept in
sync. Partially addresses PR kern/37437.

1.175 Thu Apr 24 18:39:21 GMT 2008 ad branches: 1.175.2; 1.175.4; 1.175.8;
Merge proc::p_mutex and proc::p_smutex into a single adaptive mutex, since
we no longer need to guard against access from hardware interrupt handlers.

Additionally, if cloning a process with CLONE_SIGHAND, arrange to have the
child process share the parent's lock so that signal state may be kept in
sync. Partially addresses PR kern/37437.

/src/sys/kern/
H A Dkern_resource.c1.175 Wed Jul 13 09:52:00 GMT 2016 njoly branches: 1.175.2; 1.175.4;
In dosetrlimit() round stack hard limit just like soft one.
Avoid cases where hard limit becomes smaller than soft limit.

1.175 Wed Jul 13 09:52:00 GMT 2016 njoly branches: 1.175.2; 1.175.4;
In dosetrlimit() round stack hard limit just like soft one.
Avoid cases where hard limit becomes smaller than soft limit.

1.175 Wed Jul 13 09:52:00 GMT 2016 njoly branches: 1.175.2; 1.175.4;
In dosetrlimit() round stack hard limit just like soft one.
Avoid cases where hard limit becomes smaller than soft limit.

H A Dsys_process.c1.175 Wed Nov 02 00:11:59 GMT 2016 pgoyette branches: 1.175.2;
* Split sys/kern/sys_process.c into three parts:
1 - ptrace(2) syscall for native emulation
2 - common ptrace(2) syscall code (shared with compat_netbsd32)
3 - support routines that are shared with PROCFS and/or KTRACE

* Add module glue for #1 and #2. Both modules will be built-in to the
kernel if "options PTRACE" is included in the config file (this is
the default, defined in sys/conf/std).

* Mark the ptrace(2) syscall as modular in syscalls.master (generated
files will be committed shortly).

* Conditionalize all remaining portions of PTRACE code on a new kernel
option PTRACE_HOOKS.

XXX Instead of PROCFS depending on 'options PTRACE', we should probably
just add a procfs attribute to the sys/kern/sys_process.c file's
entry in files.kern, and add PROCFS to the "#if defineds" for
process_domem(). It's really confusing to have two different ways
of requiring this file.

1.175 Wed Nov 02 00:11:59 GMT 2016 pgoyette branches: 1.175.2;
* Split sys/kern/sys_process.c into three parts:
1 - ptrace(2) syscall for native emulation
2 - common ptrace(2) syscall code (shared with compat_netbsd32)
3 - support routines that are shared with PROCFS and/or KTRACE

* Add module glue for #1 and #2. Both modules will be built-in to the
kernel if "options PTRACE" is included in the config file (this is
the default, defined in sys/conf/std).

* Mark the ptrace(2) syscall as modular in syscalls.master (generated
files will be committed shortly).

* Conditionalize all remaining portions of PTRACE code on a new kernel
option PTRACE_HOOKS.

XXX Instead of PROCFS depending on 'options PTRACE', we should probably
just add a procfs attribute to the sys/kern/sys_process.c file's
entry in files.kern, and add PROCFS to the "#if defineds" for
process_domem(). It's really confusing to have two different ways
of requiring this file.

H A Dinit_sysctl.c1.175 Thu Jul 01 02:38:30 GMT 2010 rmind branches: 1.175.2; 1.175.4;
Remove pfind() and pgfind(), fix locking in various broken uses of these.
Rename real routines to proc_find() and pgrp_find(), remove PFIND_* flags
and have consistent behaviour. Provide proc_find_raw() for special cases.
Fix memory leak in sysctl_proc_corename().

COMPAT_LINUX: rework ptrace() locking, minimise differences between
different versions per-arch.

Note: while this change adds some formal cosmetics for COMPAT_DARWIN and
COMPAT_IRIX - locking there is utterly broken (for ages).

Fixes PR/43176.

1.175 Thu Jul 01 02:38:30 GMT 2010 rmind branches: 1.175.2; 1.175.4;
Remove pfind() and pgfind(), fix locking in various broken uses of these.
Rename real routines to proc_find() and pgrp_find(), remove PFIND_* flags
and have consistent behaviour. Provide proc_find_raw() for special cases.
Fix memory leak in sysctl_proc_corename().

COMPAT_LINUX: rework ptrace() locking, minimise differences between
different versions per-arch.

Note: while this change adds some formal cosmetics for COMPAT_DARWIN and
COMPAT_IRIX - locking there is utterly broken (for ages).

Fixes PR/43176.

1.175 Thu Jul 01 02:38:30 GMT 2010 rmind branches: 1.175.2; 1.175.4;
Remove pfind() and pgfind(), fix locking in various broken uses of these.
Rename real routines to proc_find() and pgrp_find(), remove PFIND_* flags
and have consistent behaviour. Provide proc_find_raw() for special cases.
Fix memory leak in sysctl_proc_corename().

COMPAT_LINUX: rework ptrace() locking, minimise differences between
different versions per-arch.

Note: while this change adds some formal cosmetics for COMPAT_DARWIN and
COMPAT_IRIX - locking there is utterly broken (for ages).

Fixes PR/43176.

H A Dvfs_bio.c1.175 Sun Jul 29 13:53:46 GMT 2007 ad branches: 1.175.4; 1.175.6;
B_ERROR is gone.
1.175 Sun Jul 29 13:53:46 GMT 2007 ad branches: 1.175.4; 1.175.6;
B_ERROR is gone.
1.175 Sun Jul 29 13:53:46 GMT 2007 ad branches: 1.175.4; 1.175.6;
B_ERROR is gone.
/src/sys/arch/vax/conf/
H A DGENERIC1.175 Sun Aug 08 18:19:26 GMT 2010 chs branches: 1.175.2; 1.175.4;
enable DDB_HISTORY_SIZE since DDB is enabled.

1.175 Sun Aug 08 18:19:26 GMT 2010 chs branches: 1.175.2; 1.175.4;
enable DDB_HISTORY_SIZE since DDB is enabled.

1.175 Sun Aug 08 18:19:26 GMT 2010 chs branches: 1.175.2; 1.175.4;
enable DDB_HISTORY_SIZE since DDB is enabled.

/src/sys/arch/vax/vax/
H A Dpmap.c1.175 Fri Nov 27 03:23:14 GMT 2009 rmind branches: 1.175.2; 1.175.4;
- Use uvm_lwp_setuarea() instead of directly setting address to lwp_t::l_addr.
- Replace most remaining uses of l_addr with uvm_lwp_getuarea() or lwp_getpcb().
- Amend assembly in ports where it accesses PCB via struct user.
- Rename L_ADDR to L_PCB in few places. Reduce sys/user.h inclusions.

1.175 Fri Nov 27 03:23:14 GMT 2009 rmind branches: 1.175.2; 1.175.4;
- Use uvm_lwp_setuarea() instead of directly setting address to lwp_t::l_addr.
- Replace most remaining uses of l_addr with uvm_lwp_getuarea() or lwp_getpcb().
- Amend assembly in ports where it accesses PCB via struct user.
- Rename L_ADDR to L_PCB in few places. Reduce sys/user.h inclusions.

1.175 Fri Nov 27 03:23:14 GMT 2009 rmind branches: 1.175.2; 1.175.4;
- Use uvm_lwp_setuarea() instead of directly setting address to lwp_t::l_addr.
- Replace most remaining uses of l_addr with uvm_lwp_getuarea() or lwp_getpcb().
- Amend assembly in ports where it accesses PCB via struct user.
- Rename L_ADDR to L_PCB in few places. Reduce sys/user.h inclusions.

/src/sys/arch/atari/atari/
H A Dmachdep.c1.175 Fri Aug 10 17:43:32 GMT 2012 tsutsui branches: 1.175.2; 1.175.4;
Appease gcc -fno-common:
- remove physmem from machdep.c since it's initialized in atari_init.c
- declare I/O address space variables properly
Compile test only. (currenty my TT030 is busy on pkgsrc builds)

1.175 Fri Aug 10 17:43:32 GMT 2012 tsutsui branches: 1.175.2; 1.175.4;
Appease gcc -fno-common:
- remove physmem from machdep.c since it's initialized in atari_init.c
- declare I/O address space variables properly
Compile test only. (currenty my TT030 is busy on pkgsrc builds)

1.175 Fri Aug 10 17:43:32 GMT 2012 tsutsui branches: 1.175.2; 1.175.4;
Appease gcc -fno-common:
- remove physmem from machdep.c since it's initialized in atari_init.c
- declare I/O address space variables properly
Compile test only. (currenty my TT030 is busy on pkgsrc builds)

/src/sys/arch/arm/arm/
H A Dcpufunc.c1.175 Sat Oct 20 06:35:34 GMT 2018 skrll branches: 1.175.4; 1.175.6;
Clean up around cpu_ttb and fix a bunch of builds

1.175 Sat Oct 20 06:35:34 GMT 2018 skrll branches: 1.175.4; 1.175.6;
Clean up around cpu_ttb and fix a bunch of builds

1.175 Sat Oct 20 06:35:34 GMT 2018 skrll branches: 1.175.4; 1.175.6;
Clean up around cpu_ttb and fix a bunch of builds

/src/sys/nfs/
H A Dnfs_bio.c1.175 Thu Apr 24 15:35:31 GMT 2008 ad branches: 1.175.2; 1.175.8;
Network protocol interrupts can now block on locks, so merge the globals
proclist_mutex and proclist_lock into a single adaptive mutex (proc_lock).
Implications:

- Inspecting process state requires thread context, so signals can no longer
be sent from a hardware interrupt handler. Signal activity must be
deferred to a soft interrupt or kthread.

- As the proc state locking is simplified, it's now safe to take exit()
and wait() out from under kernel_lock.

- The system spends less time at IPL_SCHED, and there is less lock activity.

1.175 Thu Apr 24 15:35:31 GMT 2008 ad branches: 1.175.2; 1.175.8;
Network protocol interrupts can now block on locks, so merge the globals
proclist_mutex and proclist_lock into a single adaptive mutex (proc_lock).
Implications:

- Inspecting process state requires thread context, so signals can no longer
be sent from a hardware interrupt handler. Signal activity must be
deferred to a soft interrupt or kthread.

- As the proc state locking is simplified, it's now safe to take exit()
and wait() out from under kernel_lock.

- The system spends less time at IPL_SCHED, and there is less lock activity.

1.175 Thu Apr 24 15:35:31 GMT 2008 ad branches: 1.175.2; 1.175.8;
Network protocol interrupts can now block on locks, so merge the globals
proclist_mutex and proclist_lock into a single adaptive mutex (proc_lock).
Implications:

- Inspecting process state requires thread context, so signals can no longer
be sent from a hardware interrupt handler. Signal activity must be
deferred to a soft interrupt or kthread.

- As the proc state locking is simplified, it's now safe to take exit()
and wait() out from under kernel_lock.

- The system spends less time at IPL_SCHED, and there is less lock activity.

/src/sys/sys/
H A Dsysctl.h1.175 Fri Feb 29 06:37:57 GMT 2008 matt branches: 1.175.2; 1.175.4; 1.175.6;
#include <stdbool.h> if !_KERNEL && !_STANDALONE

1.175 Fri Feb 29 06:37:57 GMT 2008 matt branches: 1.175.2; 1.175.4; 1.175.6;
#include <stdbool.h> if !_KERNEL && !_STANDALONE

1.175 Fri Feb 29 06:37:57 GMT 2008 matt branches: 1.175.2; 1.175.4; 1.175.6;
#include <stdbool.h> if !_KERNEL && !_STANDALONE

1.175 Fri Feb 29 06:37:57 GMT 2008 matt branches: 1.175.2; 1.175.4; 1.175.6;
#include <stdbool.h> if !_KERNEL && !_STANDALONE

/src/sys/ddb/
H A Ddb_command.c1.175 Fri Oct 30 16:29:49 GMT 2020 skrll branches: 1.175.2;
Remove "also;"

1.175 Fri Oct 30 16:29:49 GMT 2020 skrll branches: 1.175.2;
Remove "also;"

/src/etc/mtree/
H A Dspecial1.175 Mon Jun 06 10:56:28 GMT 2022 nia branches: 1.175.2;
build system: Revert all the recent additions of MK[...] knobs that
allow conditionally disabling the building of certain user space
programs in the 'base' set.

There is not enough consensus that this is the right way and a few
people had strong objections, see source-changes-d@.

1.175 Mon Jun 06 10:56:28 GMT 2022 nia branches: 1.175.2;
build system: Revert all the recent additions of MK[...] knobs that
allow conditionally disabling the building of certain user space
programs in the 'base' set.

There is not enough consensus that this is the right way and a few
people had strong objections, see source-changes-d@.

/src/sys/arch/macppc/macppc/
H A Dmachdep.c1.175 Sun Jun 26 09:23:32 GMT 2022 martin branches: 1.175.4;
cpu_reboot: use cpu_halt_others() instead of a (simple) open coded
version of it.

1.175 Sun Jun 26 09:23:32 GMT 2022 martin branches: 1.175.4;
cpu_reboot: use cpu_halt_others() instead of a (simple) open coded
version of it.

/src/sys/ufs/lfs/
H A Dlfs_syscalls.c1.175 Wed Jul 26 16:42:37 GMT 2017 maya branches: 1.175.4; 1.175.10;
change lfs_nextsegsleep and lfs_allclean_wakeup to use condvar

XXX had to use lfs_lock in lfs_segwait, removed kernel_lock, is this
appropriate?

1.175 Wed Jul 26 16:42:37 GMT 2017 maya branches: 1.175.4; 1.175.10;
change lfs_nextsegsleep and lfs_allclean_wakeup to use condvar

XXX had to use lfs_lock in lfs_segwait, removed kernel_lock, is this
appropriate?

1.175 Wed Jul 26 16:42:37 GMT 2017 maya branches: 1.175.4; 1.175.10;
change lfs_nextsegsleep and lfs_allclean_wakeup to use condvar

XXX had to use lfs_lock in lfs_segwait, removed kernel_lock, is this
appropriate?

/src/sys/arch/sparc64/sparc64/
H A Dmachdep.c1.178 Fri Mar 04 22:04:51 GMT 2005 scw Undo revision 1.175 (hi jason!) to prevent a buzz-loop in
bus_dmamap_load_mbuf(). This implementation already dealt
with zero length mbufs.

Addresses port-sparc64/29473
1.175 Sun Nov 28 17:34:46 GMT 2004 thorpej branches: 1.175.4;
bus_dmamap_load_mbuf(): Skip zero-length mbufs.
kern/24811
1.175 Sun Nov 28 17:34:46 GMT 2004 thorpej branches: 1.175.4;
bus_dmamap_load_mbuf(): Skip zero-length mbufs.
kern/24811
/src/sys/dev/usb/
H A Dohci.c1.175 Sun Sep 03 07:06:39 GMT 2006 christos branches: 1.175.2; 1.175.4;
use c99 initializers
1.175 Sun Sep 03 07:06:39 GMT 2006 christos branches: 1.175.2; 1.175.4;
use c99 initializers
1.175 Sun Sep 03 07:06:39 GMT 2006 christos branches: 1.175.2; 1.175.4;
use c99 initializers
H A Dusbdi.c1.175 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.175.2; 1.175.4;
Update the kernhist(9) kernel history code to address issues identified
in PR kern/52639, as well as some general cleaning-up...

(As proposed on tech-kern@ with additional changes and enhancements.)

Details of changes:

* All history arguments are now stored as uintmax_t values[1], both in
the kernel and in the structures used for exporting the history data
to userland via sysctl(9). This avoids problems on some architectures
where passing a 64-bit (or larger) value to printf(3) can cause it to
process the value as multiple arguments. (This can be particularly
problematic when printf()'s format string is not a literal, since in
that case the compiler cannot know how large each argument should be.)

* Update the data structures used for exporting kernel history data to
include a version number as well as the length of history arguments.

* All [2] existing users of kernhist(9) have had their format strings
updated. Each format specifier now includes an explicit length
modifier 'j' to refer to numeric values of the size of uintmax_t.

* All [2] existing users of kernhist(9) have had their format strings
updated to replace uses of "%p" with "%#jx", and the pointer
arguments are now cast to (uintptr_t) before being subsequently cast
to (uintmax_t). This is needed to avoid compiler warnings about
casting "pointer to integer of a different size."

* All [2] existing users of kernhist(9) have had instances of "%s" or
"%c" format strings replaced with numeric formats; several instances
of mis-match between format string and argument list have been fixed.

* vmstat(1) has been modified to handle the new size of arguments in the
history data as exported by sysctl(9).

* vmstat(1) now provides a warning message if the history requested with
the -u option does not exist (previously, this condition was silently
ignored, with only a single blank line being printed).

* vmstat(1) now checks the version and argument length included in the
data exported via sysctl(9) and exits if they do not match the values
with which vmstat was built.

* The kernhist(9) man-page has been updated to note the additional
requirements imposed on the format strings, along with several other
minor changes and enhancements.

[1] It would have been possible to use an explicit length (for example,
uint64_t) for the history arguments. But that would require another
"rototill" of all the users in the future when we add support for an
architecture that supports a larger size. Also, the printf(3) format
specifiers for explicitly-sized values, such as "%"PRIu64, are much
more verbose (and less aesthetically appealing, IMHO) than simply
using "%ju".

[2] I've tried very hard to find "all [the] existing users of kernhist(9)"
but it is possible that I've missed some of them. I would be glad to
update any stragglers that anyone identifies.

1.175 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.175.2; 1.175.4;
Update the kernhist(9) kernel history code to address issues identified
in PR kern/52639, as well as some general cleaning-up...

(As proposed on tech-kern@ with additional changes and enhancements.)

Details of changes:

* All history arguments are now stored as uintmax_t values[1], both in
the kernel and in the structures used for exporting the history data
to userland via sysctl(9). This avoids problems on some architectures
where passing a 64-bit (or larger) value to printf(3) can cause it to
process the value as multiple arguments. (This can be particularly
problematic when printf()'s format string is not a literal, since in
that case the compiler cannot know how large each argument should be.)

* Update the data structures used for exporting kernel history data to
include a version number as well as the length of history arguments.

* All [2] existing users of kernhist(9) have had their format strings
updated. Each format specifier now includes an explicit length
modifier 'j' to refer to numeric values of the size of uintmax_t.

* All [2] existing users of kernhist(9) have had their format strings
updated to replace uses of "%p" with "%#jx", and the pointer
arguments are now cast to (uintptr_t) before being subsequently cast
to (uintmax_t). This is needed to avoid compiler warnings about
casting "pointer to integer of a different size."

* All [2] existing users of kernhist(9) have had instances of "%s" or
"%c" format strings replaced with numeric formats; several instances
of mis-match between format string and argument list have been fixed.

* vmstat(1) has been modified to handle the new size of arguments in the
history data as exported by sysctl(9).

* vmstat(1) now provides a warning message if the history requested with
the -u option does not exist (previously, this condition was silently
ignored, with only a single blank line being printed).

* vmstat(1) now checks the version and argument length included in the
data exported via sysctl(9) and exits if they do not match the values
with which vmstat was built.

* The kernhist(9) man-page has been updated to note the additional
requirements imposed on the format strings, along with several other
minor changes and enhancements.

[1] It would have been possible to use an explicit length (for example,
uint64_t) for the history arguments. But that would require another
"rototill" of all the users in the future when we add support for an
architecture that supports a larger size. Also, the printf(3) format
specifiers for explicitly-sized values, such as "%"PRIu64, are much
more verbose (and less aesthetically appealing, IMHO) than simply
using "%ju".

[2] I've tried very hard to find "all [the] existing users of kernhist(9)"
but it is possible that I've missed some of them. I would be glad to
update any stragglers that anyone identifies.

1.175 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.175.2; 1.175.4;
Update the kernhist(9) kernel history code to address issues identified
in PR kern/52639, as well as some general cleaning-up...

(As proposed on tech-kern@ with additional changes and enhancements.)

Details of changes:

* All history arguments are now stored as uintmax_t values[1], both in
the kernel and in the structures used for exporting the history data
to userland via sysctl(9). This avoids problems on some architectures
where passing a 64-bit (or larger) value to printf(3) can cause it to
process the value as multiple arguments. (This can be particularly
problematic when printf()'s format string is not a literal, since in
that case the compiler cannot know how large each argument should be.)

* Update the data structures used for exporting kernel history data to
include a version number as well as the length of history arguments.

* All [2] existing users of kernhist(9) have had their format strings
updated. Each format specifier now includes an explicit length
modifier 'j' to refer to numeric values of the size of uintmax_t.

* All [2] existing users of kernhist(9) have had their format strings
updated to replace uses of "%p" with "%#jx", and the pointer
arguments are now cast to (uintptr_t) before being subsequently cast
to (uintmax_t). This is needed to avoid compiler warnings about
casting "pointer to integer of a different size."

* All [2] existing users of kernhist(9) have had instances of "%s" or
"%c" format strings replaced with numeric formats; several instances
of mis-match between format string and argument list have been fixed.

* vmstat(1) has been modified to handle the new size of arguments in the
history data as exported by sysctl(9).

* vmstat(1) now provides a warning message if the history requested with
the -u option does not exist (previously, this condition was silently
ignored, with only a single blank line being printed).

* vmstat(1) now checks the version and argument length included in the
data exported via sysctl(9) and exits if they do not match the values
with which vmstat was built.

* The kernhist(9) man-page has been updated to note the additional
requirements imposed on the format strings, along with several other
minor changes and enhancements.

[1] It would have been possible to use an explicit length (for example,
uint64_t) for the history arguments. But that would require another
"rototill" of all the users in the future when we add support for an
architecture that supports a larger size. Also, the printf(3) format
specifiers for explicitly-sized values, such as "%"PRIu64, are much
more verbose (and less aesthetically appealing, IMHO) than simply
using "%ju".

[2] I've tried very hard to find "all [the] existing users of kernhist(9)"
but it is possible that I've missed some of them. I would be glad to
update any stragglers that anyone identifies.

/src/sys/dev/
H A Dvnd.c1.175 Wed Jan 02 11:48:36 GMT 2008 ad branches: 1.175.2; 1.175.6;
Merge vmlocking2 to head.
1.175 Wed Jan 02 11:48:36 GMT 2008 ad branches: 1.175.2; 1.175.6;
Merge vmlocking2 to head.
1.175 Wed Jan 02 11:48:36 GMT 2008 ad branches: 1.175.2; 1.175.6;
Merge vmlocking2 to head.
/src/sys/netinet/
H A Dtcp_output.c1.175 Wed Jun 05 19:01:26 GMT 2013 christos branches: 1.175.2; 1.175.6;
IPSEC has not come in two speeds for a long time now (IPSEC == kame,
FAST_IPSEC). Make everything refer to IPSEC to avoid confusion.

1.175 Wed Jun 05 19:01:26 GMT 2013 christos branches: 1.175.2; 1.175.6;
IPSEC has not come in two speeds for a long time now (IPSEC == kame,
FAST_IPSEC). Make everything refer to IPSEC to avoid confusion.

1.175 Wed Jun 05 19:01:26 GMT 2013 christos branches: 1.175.2; 1.175.6;
IPSEC has not come in two speeds for a long time now (IPSEC == kame,
FAST_IPSEC). Make everything refer to IPSEC to avoid confusion.

H A Dtcp_var.h1.175 Thu Jul 31 03:39:35 GMT 2014 rtr branches: 1.175.2; 1.175.4;
split PRU_DISCONNECT, PRU_SHUTDOWN and PRU_ABORT function out of
pr_generic() usrreq switches and put into separate functions

xxx_disconnect(struct socket *)
xxx_shutdown(struct socket *)
xxx_abort(struct socket *)

- always KASSERT(solocked(so)) even if not implemented
- replace calls to pr_generic() with req =
PRU_{DISCONNECT,SHUTDOWN,ABORT}
with calls to pr_{disconnect,shutdown,abort}() respectively

rename existing internal functions used to implement above functionality
to permit use of the names for xxx_{disconnect,shutdown,abort}().

- {l2cap,sco,rfcomm}_disconnect() ->
{l2cap,sco,rfcomm}_disconnect_pcb()
- {unp,rip,tcp}_disconnect() -> {unp,rip,tcp}_disconnect1()
- unp_shutdown() -> unp_shutdown1()

patch reviewed by rmind

1.175 Thu Jul 31 03:39:35 GMT 2014 rtr branches: 1.175.2; 1.175.4;
split PRU_DISCONNECT, PRU_SHUTDOWN and PRU_ABORT function out of
pr_generic() usrreq switches and put into separate functions

xxx_disconnect(struct socket *)
xxx_shutdown(struct socket *)
xxx_abort(struct socket *)

- always KASSERT(solocked(so)) even if not implemented
- replace calls to pr_generic() with req =
PRU_{DISCONNECT,SHUTDOWN,ABORT}
with calls to pr_{disconnect,shutdown,abort}() respectively

rename existing internal functions used to implement above functionality
to permit use of the names for xxx_{disconnect,shutdown,abort}().

- {l2cap,sco,rfcomm}_disconnect() ->
{l2cap,sco,rfcomm}_disconnect_pcb()
- {unp,rip,tcp}_disconnect() -> {unp,rip,tcp}_disconnect1()
- unp_shutdown() -> unp_shutdown1()

patch reviewed by rmind

1.175 Thu Jul 31 03:39:35 GMT 2014 rtr branches: 1.175.2; 1.175.4;
split PRU_DISCONNECT, PRU_SHUTDOWN and PRU_ABORT function out of
pr_generic() usrreq switches and put into separate functions

xxx_disconnect(struct socket *)
xxx_shutdown(struct socket *)
xxx_abort(struct socket *)

- always KASSERT(solocked(so)) even if not implemented
- replace calls to pr_generic() with req =
PRU_{DISCONNECT,SHUTDOWN,ABORT}
with calls to pr_{disconnect,shutdown,abort}() respectively

rename existing internal functions used to implement above functionality
to permit use of the names for xxx_{disconnect,shutdown,abort}().

- {l2cap,sco,rfcomm}_disconnect() ->
{l2cap,sco,rfcomm}_disconnect_pcb()
- {unp,rip,tcp}_disconnect() -> {unp,rip,tcp}_disconnect1()
- unp_shutdown() -> unp_shutdown1()

patch reviewed by rmind

/src/sys/uvm/
H A Duvm_glue.c1.175 Tue Dec 31 22:42:51 GMT 2019 ad branches: 1.175.2;
- Add and use wrapper functions that take and acquire page interlocks, and pairs
of page interlocks. Require that the page interlock be held over calls to
uvm_pageactivate(), uvm_pagewire() and similar.

- Solve the concurrency problem with page replacement state. Rather than
updating the global state synchronously, set an intended state on
individual pages (active, inactive, enqueued, dequeued) while holding the
page interlock. After the interlock is released put the pages on a 128
entry per-CPU queue for their state changes to be made real in batch.
This results in in a ~400 fold decrease in contention on my test system.
Proposed on tech-kern but modified to use the page interlock rather than
atomics to synchronise as it's much easier to maintain that way, and
cheaper.

1.175 Tue Dec 31 22:42:51 GMT 2019 ad branches: 1.175.2;
- Add and use wrapper functions that take and acquire page interlocks, and pairs
of page interlocks. Require that the page interlock be held over calls to
uvm_pageactivate(), uvm_pagewire() and similar.

- Solve the concurrency problem with page replacement state. Rather than
updating the global state synchronously, set an intended state on
individual pages (active, inactive, enqueued, dequeued) while holding the
page interlock. After the interlock is released put the pages on a 128
entry per-CPU queue for their state changes to be made real in batch.
This results in in a ~400 fold decrease in contention on my test system.
Proposed on tech-kern but modified to use the page interlock rather than
atomics to synchronise as it's much easier to maintain that way, and
cheaper.

H A Duvm_mmap.c1.175 Sun Feb 23 15:46:43 GMT 2020 ad branches: 1.175.10;
UVM locking changes, proposed on tech-kern:

- Change the lock on uvm_object, vm_amap and vm_anon to be a RW lock.
- Break v_interlock and vmobjlock apart. v_interlock remains a mutex.
- Do partial PV list locking in the x86 pmap. Others to follow later.

1.175 Sun Feb 23 15:46:43 GMT 2020 ad branches: 1.175.10;
UVM locking changes, proposed on tech-kern:

- Change the lock on uvm_object, vm_amap and vm_anon to be a RW lock.
- Break v_interlock and vmobjlock apart. v_interlock remains a mutex.
- Do partial PV list locking in the x86 pmap. Others to follow later.

Completed in 267 milliseconds

1234567891011>>