Searched hist:1.168 (Results 1 - 25 of 352) sorted by relevance

1234567891011>>

/src/sys/arch/x86/x86/
H A Dintr.c1.168 Mon Apr 22 22:29:28 GMT 2024 andvar branches: 1.168.2;
Add opt_pci.h include to fix NO_PCI_MSI_MSIX build.
(Path from Paolo Pisati in current_users@)

While here:
Simplify mp_cpu_start() ifdefs. MULTIPROCESSOR and HYPERV code falls under
NLAPIC > 0, thus just combine all blocks under this guard.
Rearrange opt_acpi.h include alphabetically.

1.168 Mon Apr 22 22:29:28 GMT 2024 andvar branches: 1.168.2;
Add opt_pci.h include to fix NO_PCI_MSI_MSIX build.
(Path from Paolo Pisati in current_users@)

While here:
Simplify mp_cpu_start() ifdefs. MULTIPROCESSOR and HYPERV code falls under
NLAPIC > 0, thus just combine all blocks under this guard.
Rearrange opt_acpi.h include alphabetically.

/src/sys/compat/sunos/
H A Dsunos_misc.c1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

1.168 Thu Jun 24 13:03:07 GMT 2010 hannken branches: 1.168.14; 1.168.18; 1.168.20; 1.168.28; 1.168.34; 1.168.36; 1.168.40;
Clean up vnode lock operations pass 2:

VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.

Welcome to 5.99.32.

Discussed on tech-kern.

/src/sys/sys/
H A Dsyscallargs.h1.168 Tue Jul 17 18:03:10 GMT 2007 joerg branches: 1.168.2; 1.168.6;
Regen.

1.168 Tue Jul 17 18:03:10 GMT 2007 joerg branches: 1.168.2; 1.168.6;
Regen.

1.168 Tue Jul 17 18:03:10 GMT 2007 joerg branches: 1.168.2; 1.168.6;
Regen.

H A Dlwp.h1.168 Fri Mar 29 01:09:45 GMT 2013 christos branches: 1.168.4; 1.168.8;
prototype adjustments for lwp_park, welcome to 6.99.19

1.168 Fri Mar 29 01:09:45 GMT 2013 christos branches: 1.168.4; 1.168.8;
prototype adjustments for lwp_park, welcome to 6.99.19

1.168 Fri Mar 29 01:09:45 GMT 2013 christos branches: 1.168.4; 1.168.8;
prototype adjustments for lwp_park, welcome to 6.99.19

/src/sys/arch/sparc64/sparc64/
H A Dtrap.c1.168 Sat Jul 30 19:29:12 GMT 2011 martin branches: 1.168.2; 1.168.6; 1.168.8;
Get rid of #ifdef __sparc__ in uvm code - as noted by cgd back 1996,
now that we have __HAVE_CPU_VMSPACE_EXEC/cpu_vmspace_exec().

1.168 Sat Jul 30 19:29:12 GMT 2011 martin branches: 1.168.2; 1.168.6; 1.168.8;
Get rid of #ifdef __sparc__ in uvm code - as noted by cgd back 1996,
now that we have __HAVE_CPU_VMSPACE_EXEC/cpu_vmspace_exec().

1.168 Sat Jul 30 19:29:12 GMT 2011 martin branches: 1.168.2; 1.168.6; 1.168.8;
Get rid of #ifdef __sparc__ in uvm code - as noted by cgd back 1996,
now that we have __HAVE_CPU_VMSPACE_EXEC/cpu_vmspace_exec().

1.168 Sat Jul 30 19:29:12 GMT 2011 martin branches: 1.168.2; 1.168.6; 1.168.8;
Get rid of #ifdef __sparc__ in uvm code - as noted by cgd back 1996,
now that we have __HAVE_CPU_VMSPACE_EXEC/cpu_vmspace_exec().

/src/sys/dev/mii/
H A Dmiidevs1.168 Tue Jun 23 14:35:36 GMT 2020 msaitoh branches: 1.168.20;
Add some Microsemi (Vitesse) devices.

1.168 Tue Jun 23 14:35:36 GMT 2020 msaitoh branches: 1.168.20;
Add some Microsemi (Vitesse) devices.

H A Dmiidevs.h1.168 Fri Sep 29 09:08:30 GMT 2023 msaitoh Regen.

/src/sys/arch/atari/atari/
H A Dmachdep.c1.168 Sat Oct 16 17:10:42 GMT 2010 tsutsui branches: 1.168.2; 1.168.4;
Prepare empty module_init_md() for options MODULAR for all other m68k ports.

1.168 Sat Oct 16 17:10:42 GMT 2010 tsutsui branches: 1.168.2; 1.168.4;
Prepare empty module_init_md() for options MODULAR for all other m68k ports.

1.168 Sat Oct 16 17:10:42 GMT 2010 tsutsui branches: 1.168.2; 1.168.4;
Prepare empty module_init_md() for options MODULAR for all other m68k ports.

/src/sys/compat/netbsd32/
H A Dnetbsd32_netbsd.c1.168 Fri Nov 19 06:44:37 GMT 2010 dholland branches: 1.168.2; 1.168.4;
Introduce struct pathbuf. This is an abstraction to hold a pathname
and the metadata required to interpret it. Callers of namei must now
create a pathbuf and pass it to NDINIT (instead of a string and a
uio_seg), then destroy the pathbuf after the namei session is
complete.

Update all namei call sites accordingly. Add a pathbuf(9) man page and
update namei(9).

The pathbuf interface also now appears in a couple of related
additional places that were passing string/uio_seg pairs that were
later fed into NDINIT. Update other call sites accordingly.

1.168 Fri Nov 19 06:44:37 GMT 2010 dholland branches: 1.168.2; 1.168.4;
Introduce struct pathbuf. This is an abstraction to hold a pathname
and the metadata required to interpret it. Callers of namei must now
create a pathbuf and pass it to NDINIT (instead of a string and a
uio_seg), then destroy the pathbuf after the namei session is
complete.

Update all namei call sites accordingly. Add a pathbuf(9) man page and
update namei(9).

The pathbuf interface also now appears in a couple of related
additional places that were passing string/uio_seg pairs that were
later fed into NDINIT. Update other call sites accordingly.

1.168 Fri Nov 19 06:44:37 GMT 2010 dholland branches: 1.168.2; 1.168.4;
Introduce struct pathbuf. This is an abstraction to hold a pathname
and the metadata required to interpret it. Callers of namei must now
create a pathbuf and pass it to NDINIT (instead of a string and a
uio_seg), then destroy the pathbuf after the namei session is
complete.

Update all namei call sites accordingly. Add a pathbuf(9) man page and
update namei(9).

The pathbuf interface also now appears in a couple of related
additional places that were passing string/uio_seg pairs that were
later fed into NDINIT. Update other call sites accordingly.

/src/sys/arch/sparc/sparc/
H A Dautoconf.c1.168 Tue Apr 02 06:39:32 GMT 2002 chs branches: 1.168.2; 1.168.4;
make this compile with DEBUG.

1.168 Tue Apr 02 06:39:32 GMT 2002 chs branches: 1.168.2; 1.168.4;
make this compile with DEBUG.

1.168 Tue Apr 02 06:39:32 GMT 2002 chs branches: 1.168.2; 1.168.4;
make this compile with DEBUG.

/src/sys/arch/alpha/conf/
H A Dfiles.alpha1.168 Sun Dec 11 00:16:16 GMT 2005 christos branches: 1.168.4; 1.168.8;
merge ktrace-lwp.

1.168 Sun Dec 11 00:16:16 GMT 2005 christos branches: 1.168.4; 1.168.8;
merge ktrace-lwp.

1.168 Sun Dec 11 00:16:16 GMT 2005 christos branches: 1.168.4; 1.168.8;
merge ktrace-lwp.

/src/sys/dev/usb/
H A Dusb.c1.168 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.168.2; 1.168.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.168 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.168.2; 1.168.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.168 Sat Oct 28 00:37:12 GMT 2017 pgoyette branches: 1.168.2; 1.168.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/arch/mac68k/conf/
H A DGENERIC1.168 Tue Dec 20 05:35:29 GMT 2005 thorpej branches: 1.168.2; 1.168.4;
Remove the tablet line discipline.

1.168 Tue Dec 20 05:35:29 GMT 2005 thorpej branches: 1.168.2; 1.168.4;
Remove the tablet line discipline.

1.168 Tue Dec 20 05:35:29 GMT 2005 thorpej branches: 1.168.2; 1.168.4;
Remove the tablet line discipline.

/src/sys/net/
H A Dbpf.c1.168 Fri Dec 16 03:05:23 GMT 2011 christos branches: 1.168.2; 1.168.6; 1.168.8;
make comment reflect reality

1.168 Fri Dec 16 03:05:23 GMT 2011 christos branches: 1.168.2; 1.168.6; 1.168.8;
make comment reflect reality

1.168 Fri Dec 16 03:05:23 GMT 2011 christos branches: 1.168.2; 1.168.6; 1.168.8;
make comment reflect reality

1.168 Fri Dec 16 03:05:23 GMT 2011 christos branches: 1.168.2; 1.168.6; 1.168.8;
make comment reflect reality

/src/sys/kern/
H A Dmakesyscalls.sh1.168 Sun Jan 15 17:00:59 GMT 2017 christos branches: 1.168.6;
put linux_handler_t in the right place.

1.168 Sun Jan 15 17:00:59 GMT 2017 christos branches: 1.168.6;
put linux_handler_t in the right place.

H A Dsyscalls.master1.168 Tue Mar 06 16:09:21 GMT 2007 drochner branches: 1.168.2; 1.168.4;
make the first argument to profil(2) char*, for consistency with <unistd.h>

1.168 Tue Mar 06 16:09:21 GMT 2007 drochner branches: 1.168.2; 1.168.4;
make the first argument to profil(2) char*, for consistency with <unistd.h>

1.168 Tue Mar 06 16:09:21 GMT 2007 drochner branches: 1.168.2; 1.168.4;
make the first argument to profil(2) char*, for consistency with <unistd.h>

H A Dsyscalls.c1.168 Mon May 29 09:58:51 GMT 2006 drochner branches: 1.168.2;
regen

1.168 Mon May 29 09:58:51 GMT 2006 drochner branches: 1.168.2;
regen

/src/sys/arch/sun3/sun3/
H A Dpmap.c1.168 Mon Jan 07 16:58:09 GMT 2013 chs branches: 1.168.2;
switch to __USE_TOPDOWN_VM.

1.168 Mon Jan 07 16:58:09 GMT 2013 chs branches: 1.168.2;
switch to __USE_TOPDOWN_VM.

/src/sys/arch/i386/conf/
H A DMakefile.i3861.168 Wed Jan 12 23:12:12 GMT 2011 joerg branches: 1.168.2;
Allow use of traditional CPP to be set on a per platform base in sys.mk.
Honour this for dependency processing in bsd.dep.mk. Switch i386 and
amd64 assembly to use ISO C90 preprocessor concat and drop the
-traditional-cpp on this platform.
1.168 Wed Jan 12 23:12:12 GMT 2011 joerg branches: 1.168.2;
Allow use of traditional CPP to be set on a per platform base in sys.mk.
Honour this for dependency processing in bsd.dep.mk. Switch i386 and
amd64 assembly to use ISO C90 preprocessor concat and drop the
-traditional-cpp on this platform.
/src/distrib/notes/common/
H A Dcontents1.168 Fri May 27 15:43:00 GMT 2011 tsutsui branches: 1.168.4;
Remove sizes of set files. They were too hard to maintain,
while nowadays few users care about bandwidth or storage
in modern Internet environment. Ok'ed by snj@ a while ago.
1.168 Fri May 27 15:43:00 GMT 2011 tsutsui branches: 1.168.4;
Remove sizes of set files. They were too hard to maintain,
while nowadays few users care about bandwidth or storage
in modern Internet environment. Ok'ed by snj@ a while ago.
/src/share/man/man5/
H A Drc.conf.51.168 Tue Jan 09 09:17:52 GMT 2018 wiz branches: 1.168.2;
Stop using Tn.

1.168 Tue Jan 09 09:17:52 GMT 2018 wiz branches: 1.168.2;
Stop using Tn.

/src/sys/dev/pci/
H A Dpcireg.h1.168 Mon Oct 17 03:05:32 GMT 2022 mrg branches: 1.168.2;
add pcie capability and read request size linux compat, some pci root support

implement support for:
- pcie_capability_read_dword()
- pcie_capability_read_word()
- pcie_capability_write_dword()
- pcie_capability_write_word()
- pcie_get_readrq()
- pcie_set_readrq()

implement the "struct pci_dev" bus->self member by creating a minimal fake
"struct pci_dev" for the pci bus itself. this is kind of gross. it checks
that the current device's parent is a netbsd "pci" device, and that it has
a (grand) parent "ppb" device, and then fills in the fake device based upon
the pci and ppb devices.

add some PCIE_LCSR2_TGT_LSPEED encodings, and map them to linux names.
map several other PCIE_LCSR and PCIE_LCAP names.

uncomment several pcie code segments in radeon and amdgpu. (not sure that
we can test the amdgpu_si.c change, as we use the radeon version and the
amdgpu version hangs on the one machine i have.)

tested on amdgpu (RX550) and radeon (7750 & 3650).


ok @riastradh

1.168 Mon Oct 17 03:05:32 GMT 2022 mrg branches: 1.168.2;
add pcie capability and read request size linux compat, some pci root support

implement support for:
- pcie_capability_read_dword()
- pcie_capability_read_word()
- pcie_capability_write_dword()
- pcie_capability_write_word()
- pcie_get_readrq()
- pcie_set_readrq()

implement the "struct pci_dev" bus->self member by creating a minimal fake
"struct pci_dev" for the pci bus itself. this is kind of gross. it checks
that the current device's parent is a netbsd "pci" device, and that it has
a (grand) parent "ppb" device, and then fills in the fake device based upon
the pci and ppb devices.

add some PCIE_LCSR2_TGT_LSPEED encodings, and map them to linux names.
map several other PCIE_LCSR and PCIE_LCAP names.

uncomment several pcie code segments in radeon and amdgpu. (not sure that
we can test the amdgpu_si.c change, as we use the radeon version and the
amdgpu version hangs on the one machine i have.)

tested on amdgpu (RX550) and radeon (7750 & 3650).


ok @riastradh

/src/sys/uvm/
H A Duvm_extern.h1.168 Tue Jan 04 08:26:33 GMT 2011 matt branches: 1.168.2; 1.168.4;
Add better color matching selecting free pages. KM pages will now allocated
so that VA and PA have the same color. On a page fault, choose a physical
page that has the same color as the virtual address.

When allocating kernel memory pages, allow the MD to specify a preferred
VM_FREELIST from which to choose pages. For machines with large amounts
of memory (> 4GB), all kernel memory to come from <4GB to reduce the amount
of bounce buffering needed with 32bit DMA devices.
1.168 Tue Jan 04 08:26:33 GMT 2011 matt branches: 1.168.2; 1.168.4;
Add better color matching selecting free pages. KM pages will now allocated
so that VA and PA have the same color. On a page fault, choose a physical
page that has the same color as the virtual address.

When allocating kernel memory pages, allow the MD to specify a preferred
VM_FREELIST from which to choose pages. For machines with large amounts
of memory (> 4GB), all kernel memory to come from <4GB to reduce the amount
of bounce buffering needed with 32bit DMA devices.
1.168 Tue Jan 04 08:26:33 GMT 2011 matt branches: 1.168.2; 1.168.4;
Add better color matching selecting free pages. KM pages will now allocated
so that VA and PA have the same color. On a page fault, choose a physical
page that has the same color as the virtual address.

When allocating kernel memory pages, allow the MD to specify a preferred
VM_FREELIST from which to choose pages. For machines with large amounts
of memory (> 4GB), all kernel memory to come from <4GB to reduce the amount
of bounce buffering needed with 32bit DMA devices.
/src/sys/netinet/
H A Dtcp_var.h1.168 Mon Oct 31 00:52:19 GMT 2011 yamt branches: 1.168.2; 1.168.6;
tcp_reass_unlock: assertion

1.168 Mon Oct 31 00:52:19 GMT 2011 yamt branches: 1.168.2; 1.168.6;
tcp_reass_unlock: assertion

1.168 Mon Oct 31 00:52:19 GMT 2011 yamt branches: 1.168.2; 1.168.6;
tcp_reass_unlock: assertion

/src/sys/miscfs/procfs/
H A Dprocfs_vnops.c1.168 Thu Apr 24 18:39:25 GMT 2008 ad branches: 1.168.2;
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.168 Thu Apr 24 18:39:25 GMT 2008 ad branches: 1.168.2;
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.

Completed in 215 milliseconds

1234567891011>>