Searched hist:1.174 (Results 1 - 25 of 333) sorted by relevance
| /src/sys/sys/ | ||
| H A D | syscallargs.h | 1.174 Mon Nov 12 23:12:57 GMT 2007 ad branches: 1.174.2; 1.174.6; Regen. 1.174 Mon Nov 12 23:12:57 GMT 2007 ad branches: 1.174.2; 1.174.6; Regen. 1.174 Mon Nov 12 23:12:57 GMT 2007 ad branches: 1.174.2; 1.174.6; Regen. |
| H A D | syscall.h | 1.174 Fri Sep 01 21:04:45 GMT 2006 matt branches: 1.174.2; 1.174.4; Regen. (add __weak_alias(sys_ptrace, sys_nosys) when PTRACE is off) 1.174 Fri Sep 01 21:04:45 GMT 2006 matt branches: 1.174.2; 1.174.4; Regen. (add __weak_alias(sys_ptrace, sys_nosys) when PTRACE is off) 1.174 Fri Sep 01 21:04:45 GMT 2006 matt branches: 1.174.2; 1.174.4; Regen. (add __weak_alias(sys_ptrace, sys_nosys) when PTRACE is off) |
| H A D | systm.h | 1.174 Sat Oct 23 21:27:33 GMT 2004 yamt branches: 1.174.4; 1.174.6; don't reference kernel_lock directly. 1.174 Sat Oct 23 21:27:33 GMT 2004 yamt branches: 1.174.4; 1.174.6; don't reference kernel_lock directly. 1.174 Sat Oct 23 21:27:33 GMT 2004 yamt branches: 1.174.4; 1.174.6; don't reference kernel_lock directly. |
| /src/usr.bin/make/unit-tests/ | ||
| H A D | var-eval-short.exp | 1.3 Sun Mar 14 18:02:44 GMT 2021 rillig make: only evaluate the ':@' modifier if the result is actually used The test 'var-eval-short' had produced the output 'unexpected' before, on stderr. It had been generated by '${:Uword:@${FAIL}@expr@}' by combining the following obscure "features" of make: 1. the ':@' modifier loops over the words of the variable. This modifier is not really obscure, it still takes some time to get used to it. 2. the ':@' modifier allows a '$' sign in the variable name, which is useless in practice. 3. the ':@' modifier creates a temporary loop variable in the global namespace. Luckily there are only few collisions with other variable names since their naming conventions differ. 4. after looping over the words of the expression, the temporary global loop variable is deleted, and at that point the '$' is expanded, being interpreted as the start of a variable expression. 5. The ':@' modifier deleted the global variable even when it was called in parse-only mode (without VARE_WANTRES). When the modifier ':@' was initially added to make in var.c 1.40 from 2000-04-29, Var_Delete didn't expand the variable name. That feature was added in var.c 1.174 from 2013-05-18, probably without thinking of this very edge-casey combination of features. This commit fixes item 5 from the above list. The other obscurities remain for now. |
| /src/sys/arch/sparc/sparc/ | ||
| H A D | trap.c | 1.174 Sat Jan 05 22:50:12 GMT 2008 martin branches: 1.174.6; 1.174.8; Add missing include 1.174 Sat Jan 05 22:50:12 GMT 2008 martin branches: 1.174.6; 1.174.8; Add missing include 1.174 Sat Jan 05 22:50:12 GMT 2008 martin branches: 1.174.6; 1.174.8; Add missing include |
| /src/sys/dev/ic/ | ||
| H A D | tulip.c | 1.174 Tue Jan 19 22:06:25 GMT 2010 pooka branches: 1.174.2; 1.174.4; Redefine bpf linkage through an always present op vector, i.e. #if NBPFILTER is no longer required in the client. This change doesn't yet add support for loading bpf as a module, since drivers can register before bpf is attached. However, callers of bpf can now be modularized. Dynamically loadable bpf could probably be done fairly easily with coordination from the stub driver and the real driver by registering attachments in the stub before the real driver is loaded and doing a handoff. ... and I'm not going to ponder the depths of unload here. Tested with i386/MONOLITHIC, modified MONOLITHIC without bpf and rump. 1.174 Tue Jan 19 22:06:25 GMT 2010 pooka branches: 1.174.2; 1.174.4; Redefine bpf linkage through an always present op vector, i.e. #if NBPFILTER is no longer required in the client. This change doesn't yet add support for loading bpf as a module, since drivers can register before bpf is attached. However, callers of bpf can now be modularized. Dynamically loadable bpf could probably be done fairly easily with coordination from the stub driver and the real driver by registering attachments in the stub before the real driver is loaded and doing a handoff. ... and I'm not going to ponder the depths of unload here. Tested with i386/MONOLITHIC, modified MONOLITHIC without bpf and rump. 1.174 Tue Jan 19 22:06:25 GMT 2010 pooka branches: 1.174.2; 1.174.4; Redefine bpf linkage through an always present op vector, i.e. #if NBPFILTER is no longer required in the client. This change doesn't yet add support for loading bpf as a module, since drivers can register before bpf is attached. However, callers of bpf can now be modularized. Dynamically loadable bpf could probably be done fairly easily with coordination from the stub driver and the real driver by registering attachments in the stub before the real driver is loaded and doing a handoff. ... and I'm not going to ponder the depths of unload here. Tested with i386/MONOLITHIC, modified MONOLITHIC without bpf and rump. |
| /src/sys/arch/alpha/conf/ | ||
| H A D | files.alpha | 1.174 Sat Jul 21 11:59:56 GMT 2007 tsutsui branches: 1.174.4; 1.174.6; Add MI todr(9) support and timercounter(9) support with kern_cctr.c to alpha: - use todr(9) API with MI mc146818(4) driver and remove homegrown todr stuff from MD alpha/clock.c and alpha/mcclock.c - also remove obsolete cc_microtime stuff from MD code - add ci_pcc_freq member in struct cpu_info for cpu_frequency(), and calibrate it with mc146818 interval clock in mcclock attachment - call cc_init() in cpu_initclocks(9) because all alpha cpus have a pcc counter Tested on DEC 3000/300 and AlphaPC 164, but not on any SMP machines yet. 1.174 Sat Jul 21 11:59:56 GMT 2007 tsutsui branches: 1.174.4; 1.174.6; Add MI todr(9) support and timercounter(9) support with kern_cctr.c to alpha: - use todr(9) API with MI mc146818(4) driver and remove homegrown todr stuff from MD alpha/clock.c and alpha/mcclock.c - also remove obsolete cc_microtime stuff from MD code - add ci_pcc_freq member in struct cpu_info for cpu_frequency(), and calibrate it with mc146818 interval clock in mcclock attachment - call cc_init() in cpu_initclocks(9) because all alpha cpus have a pcc counter Tested on DEC 3000/300 and AlphaPC 164, but not on any SMP machines yet. 1.174 Sat Jul 21 11:59:56 GMT 2007 tsutsui branches: 1.174.4; 1.174.6; Add MI todr(9) support and timercounter(9) support with kern_cctr.c to alpha: - use todr(9) API with MI mc146818(4) driver and remove homegrown todr stuff from MD alpha/clock.c and alpha/mcclock.c - also remove obsolete cc_microtime stuff from MD code - add ci_pcc_freq member in struct cpu_info for cpu_frequency(), and calibrate it with mc146818 interval clock in mcclock attachment - call cc_init() in cpu_initclocks(9) because all alpha cpus have a pcc counter Tested on DEC 3000/300 and AlphaPC 164, but not on any SMP machines yet. |
| /src/sys/uvm/ | ||
| H A D | uvm_swap.c | 1.174 Fri Jul 08 06:45:34 GMT 2016 skrll branches: 1.174.2; 1.174.8; 1.174.10; Remove '\n' from UVMHIST_LOG format - it is not needed. 1.174 Fri Jul 08 06:45:34 GMT 2016 skrll branches: 1.174.2; 1.174.8; 1.174.10; Remove '\n' from UVMHIST_LOG format - it is not needed. 1.174 Fri Jul 08 06:45:34 GMT 2016 skrll branches: 1.174.2; 1.174.8; 1.174.10; Remove '\n' from UVMHIST_LOG format - it is not needed. 1.174 Fri Jul 08 06:45:34 GMT 2016 skrll branches: 1.174.2; 1.174.8; 1.174.10; Remove '\n' from UVMHIST_LOG format - it is not needed. |
| H A D | uvm_mmap.c | 1.174 Fri Oct 04 22:48:45 GMT 2019 kamil branches: 1.174.2; Avoid left shift changing the signedness flag Reviewed by <mrg> Reported-by: syzbot+25ac03024cedf27f3368@syzkaller.appspotmail.com 1.174 Fri Oct 04 22:48:45 GMT 2019 kamil branches: 1.174.2; Avoid left shift changing the signedness flag Reviewed by <mrg> Reported-by: syzbot+25ac03024cedf27f3368@syzkaller.appspotmail.com |
| /src/lib/libc/ | ||
| H A D | Makefile | 1.174 Mon May 29 18:25:52 GMT 2023 lukem branches: 1.174.2; libc: fix typo in comments: NO_SRSC -> NO_SRCS 1.174 Mon May 29 18:25:52 GMT 2023 lukem branches: 1.174.2; libc: fix typo in comments: NO_SRSC -> NO_SRCS |
| /src/distrib/notes/common/ | ||
| H A D | contents | 1.174 Sun Jun 24 09:38:46 GMT 2018 leot branches: 1.174.2; Fix a typo 1.174 Sun Jun 24 09:38:46 GMT 2018 leot branches: 1.174.2; Fix a typo |
| /src/distrib/sets/lists/misc/ | ||
| H A D | mi | 1.174 Thu Mar 10 13:16:58 GMT 2011 jmmv branches: 1.174.4; Enable the build of tmux and add the necessary directory and file entries. 1.174 Thu Mar 10 13:16:58 GMT 2011 jmmv branches: 1.174.4; Enable the build of tmux and add the necessary directory and file entries. |
| /src/share/man/man4/ | ||
| H A D | ddb.4 | 1.174 Mon Feb 19 10:31:53 GMT 2018 wiz branches: 1.174.2; Quote minus. 1.174 Mon Feb 19 10:31:53 GMT 2018 wiz branches: 1.174.2; Quote minus. |
| /src/sys/miscfs/specfs/ | ||
| H A D | spec_vnops.c | 1.174 Sat Jun 24 00:14:21 GMT 2017 hannken branches: 1.174.4; 1.174.6; Refuse to open a block device with zero open count when it has a mountpoint set. This may happen after forced detach or unplug of a mounted block device. 1.174 Sat Jun 24 00:14:21 GMT 2017 hannken branches: 1.174.4; 1.174.6; Refuse to open a block device with zero open count when it has a mountpoint set. This may happen after forced detach or unplug of a mounted block device. 1.174 Sat Jun 24 00:14:21 GMT 2017 hannken branches: 1.174.4; 1.174.6; Refuse to open a block device with zero open count when it has a mountpoint set. This may happen after forced detach or unplug of a mounted block device. |
| /src/sys/nfs/ | ||
| H A D | nfs_vfsops.c | 1.174 Sun Mar 04 06:03:38 GMT 2007 christos branches: 1.174.2; 1.174.4; Kill caddr_t; there will be some MI fallout, but it will be fixed shortly. 1.174 Sun Mar 04 06:03:38 GMT 2007 christos branches: 1.174.2; 1.174.4; Kill caddr_t; there will be some MI fallout, but it will be fixed shortly. 1.174 Sun Mar 04 06:03:38 GMT 2007 christos branches: 1.174.2; 1.174.4; Kill caddr_t; there will be some MI fallout, but it will be fixed shortly. |
| H A D | nfs_bio.c | 1.174 Sat Mar 29 13:48:00 GMT 2008 yamt branches: 1.174.2; ansify. from Christoph Egger. 1.174 Sat Mar 29 13:48:00 GMT 2008 yamt branches: 1.174.2; ansify. from Christoph Egger. |
| H A D | nfs_serv.c | 1.174 Thu May 03 07:28:43 GMT 2018 hannken branches: 1.174.2; nfsrv_readlink: stop attaching a zero-length mbuf for zero length symlinks. 1.174 Thu May 03 07:28:43 GMT 2018 hannken branches: 1.174.2; nfsrv_readlink: stop attaching a zero-length mbuf for zero length symlinks. |
| /src/sys/kern/ | ||
| H A D | kern_resource.c | 1.174 Sat Oct 18 08:33:29 GMT 2014 snj branches: 1.174.2; src is too big these days to tolerate superfluous apostrophes. It's "its", people! 1.174 Sat Oct 18 08:33:29 GMT 2014 snj branches: 1.174.2; src is too big these days to tolerate superfluous apostrophes. It's "its", people! |
| /src/sys/arch/x68k/conf/ | ||
| H A D | GENERIC | 1.174 Fri Jul 18 17:06:13 GMT 2014 tsutsui branches: 1.174.2; Enable NULLFS and MODULAR, and disable UMAPFS, accf_data and accf_http. No particular comments on port-x68k@. 1.174 Fri Jul 18 17:06:13 GMT 2014 tsutsui branches: 1.174.2; Enable NULLFS and MODULAR, and disable UMAPFS, accf_data and accf_http. No particular comments on port-x68k@. |
| /src/sys/arch/prep/conf/ | ||
| H A D | GENERIC | 1.174 Sun Nov 16 16:01:42 GMT 2014 manu branches: 1.174.2; Remove unused extended attributes kernel options As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them as they have been obsolete for a long time: UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate 1.174 Sun Nov 16 16:01:42 GMT 2014 manu branches: 1.174.2; Remove unused extended attributes kernel options As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them as they have been obsolete for a long time: UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate |
| /src/sys/dev/isa/ | ||
| H A D | files.isa | 1.174 Fri Oct 25 17:39:57 GMT 2019 martin branches: 1.174.2; Add support for Nuvoton NCT5104D GPIO chips, as found on PC Engines APU systems. From Andrew Doran in PR kern/54648. 1.174 Fri Oct 25 17:39:57 GMT 2019 martin branches: 1.174.2; Add support for Nuvoton NCT5104D GPIO chips, as found on PC Engines APU systems. From Andrew Doran in PR kern/54648. |
| /src/lib/libc/include/ | ||
| H A D | namespace.h | 1.174 Fri Jun 13 15:45:05 GMT 2014 joerg branches: 1.174.2; Add asysctl(3) and asysctlbyname(3) wrappers for the common idiom of fetching dynamically sized data via sysctl. 1.174 Fri Jun 13 15:45:05 GMT 2014 joerg branches: 1.174.2; Add asysctl(3) and asysctlbyname(3) wrappers for the common idiom of fetching dynamically sized data via sysctl. |
| /src/sys/arch/amd64/conf/ | ||
| H A D | ALL | 1.174 Sat Sep 24 11:05:17 GMT 2022 riastradh branches: 1.174.4; x86: Support EFI runtime services. This creates a special pmap, efi_runtime_pmap, which avoids setting PTE_U but allows mappings to lie in what would normally be user VM -- this way we don't fall afoul of SMAP/SMEP when executing EFI runtime services from CPL 0. SVS does not apply to the EFI runtime pmap. The mechanism is intended to work with either physical addressing or virtual addressing; currently the bootloader does physical addressing but in principle it could be modified to do virtual addressing instead, if it allocated virtual pages, assigned them in the memory map, and issued RT->SetVirtualAddressMap. Not sure pmap_activate_sync and pmap_deactivate_sync are correct, need more review from an x86 wizard. If this causes fallout, it can be disabled temporarily without reverting anything by just making efi_runtime_init return immediately without doing anything, or by removing options EFI_RUNTIME. amd64-only for now pending type fixes and testing on i386. 1.174 Sat Sep 24 11:05:17 GMT 2022 riastradh branches: 1.174.4; x86: Support EFI runtime services. This creates a special pmap, efi_runtime_pmap, which avoids setting PTE_U but allows mappings to lie in what would normally be user VM -- this way we don't fall afoul of SMAP/SMEP when executing EFI runtime services from CPL 0. SVS does not apply to the EFI runtime pmap. The mechanism is intended to work with either physical addressing or virtual addressing; currently the bootloader does physical addressing but in principle it could be modified to do virtual addressing instead, if it allocated virtual pages, assigned them in the memory map, and issued RT->SetVirtualAddressMap. Not sure pmap_activate_sync and pmap_deactivate_sync are correct, need more review from an x86 wizard. If this causes fallout, it can be disabled temporarily without reverting anything by just making efi_runtime_init return immediately without doing anything, or by removing options EFI_RUNTIME. amd64-only for now pending type fixes and testing on i386. |
| /src/doc/ | ||
| H A D | HACKS | 1.174 Wed Jun 15 14:11:15 GMT 2016 riastradh branches: 1.174.2; Remove dumplfs from the list now that it seems strict-aliasing-safe. 1.174 Wed Jun 15 14:11:15 GMT 2016 riastradh branches: 1.174.2; Remove dumplfs from the list now that it seems strict-aliasing-safe. |
| /src/usr.bin/ | ||
| H A D | Makefile | 1.174 Mon Jan 19 07:08:29 GMT 2009 jmmv branches: 1.174.2; Remove ATF 0.5 from dist/atf and all of the reachover Makefiles used to build it. 0.6 is going to be imported in external/bsd/atf, with all the necessary Makefiles in that same hierarchy. 1.174 Mon Jan 19 07:08:29 GMT 2009 jmmv branches: 1.174.2; Remove ATF 0.5 from dist/atf and all of the reachover Makefiles used to build it. 0.6 is going to be imported in external/bsd/atf, with all the necessary Makefiles in that same hierarchy. |
Completed in 230 milliseconds