Searched hist:1.67 (Results 1 - 25 of 1631) sorted by relevance

1234567891011>>

/src/sys/rump/librump/rumpkern/arch/x86/
H A Drump_x86_cpu_counter.c1.2 Mon Jun 15 09:09:24 GMT 2020 msaitoh Serialize rdtsc using with lfence, mfence or cpuid to read TSC more precisely.

x86/x86/tsc.c rev. 1.67 reduced cache problem and got big improvement, but it
still has room. I measured the effect of lfence, mfence, cpuid and rdtscp.
The impact to TSC skew and/or drift is:

AMD: mfence > rdtscp > cpuid > lfence-serialize > lfence = nomodify
Intel: lfence > rdtscp > cpuid > nomodify

So, mfence is the best on AMD and lfence is the best on Intel. If it has no
SSE2, we can use cpuid.

NOTE:
- An AMD's document says DE_CFG_LFENCE_SERIALIZE bit can be used for
serializing, but it's not so good.
- On Intel i386(not amd64), it seems the improvement is very little.
- rdtscp instruct can be used as serializing instruction + rdtsc, but
it's not good as [lm]fence. Both Intel and AMD's document say that
the latency of rdtscp is bigger than rdtsc, so I suspect the difference
of the result comes from it.

/src/sys/dev/isapnp/
H A Disapnpdevs.c1.67 Thu Nov 30 22:34:27 GMT 2006 christos branches: 1.67.2; 1.67.8; 1.67.10; 1.67.16;
regen
1.67 Thu Nov 30 22:34:27 GMT 2006 christos branches: 1.67.2; 1.67.8; 1.67.10; 1.67.16;
regen
1.67 Thu Nov 30 22:34:27 GMT 2006 christos branches: 1.67.2; 1.67.8; 1.67.10; 1.67.16;
regen
1.67 Thu Nov 30 22:34:27 GMT 2006 christos branches: 1.67.2; 1.67.8; 1.67.10; 1.67.16;
regen
1.67 Thu Nov 30 22:34:27 GMT 2006 christos branches: 1.67.2; 1.67.8; 1.67.10; 1.67.16;
regen
/src/sys/dev/isa/
H A Dwss.c1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

1.67 Thu Nov 16 01:33:00 GMT 2006 christos branches: 1.67.6; 1.67.8; 1.67.22; 1.67.24; 1.67.28;
__unused removal on arguments; approved by core.

H A Dpas.c1.67 Sat Mar 15 21:09:02 GMT 2008 cube branches: 1.67.4; 1.67.16; 1.67.24; 1.67.26;
Split device_t and softc for sb(4) and all its attachments.

1.67 Sat Mar 15 21:09:02 GMT 2008 cube branches: 1.67.4; 1.67.16; 1.67.24; 1.67.26;
Split device_t and softc for sb(4) and all its attachments.

1.67 Sat Mar 15 21:09:02 GMT 2008 cube branches: 1.67.4; 1.67.16; 1.67.24; 1.67.26;
Split device_t and softc for sb(4) and all its attachments.

1.67 Sat Mar 15 21:09:02 GMT 2008 cube branches: 1.67.4; 1.67.16; 1.67.24; 1.67.26;
Split device_t and softc for sb(4) and all its attachments.

1.67 Sat Mar 15 21:09:02 GMT 2008 cube branches: 1.67.4; 1.67.16; 1.67.24; 1.67.26;
Split device_t and softc for sb(4) and all its attachments.

/src/sys/dev/scsipi/
H A Dscsipi_ioctl.c1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

1.67 Thu Apr 19 17:45:20 GMT 2012 bouyer branches: 1.67.2; 1.67.14; 1.67.16; 1.67.18; 1.67.22;
Expand struct scsipi_bustype {} in a ABI-backward-compatible way to
pass more informations about the bus:
- bustype_type has 2 different bytes, one holding the existing
SCSIPI_BUSTYPE_* (scsi, atapi, ata), and one for a per-SCSIPI_BUSTYPE_*
subtype. Introduce macros to build or extract bustype_type.
- for SCSIPI_BUSTYPE_SCSI, define subtypes for parallel SCSI, Fibre Channel,
SAS and USB, to specify the transport method. SCSIPI_BUSTYPE_SCSI_PSCSI
is 0 so that bustype_type value doesn't change for existing code
- for non-SCSIPI_BUSTYPE_SCSI busses there's no defined subtype yet,
so the bustype_type value doesn't change.
- provide scsi_fc_bustype, scsi_sas_bustype and scsi_usb_bustype
along with scsi_bustype to be used by bus driver where appropriate
- scsipi_print_xfer_mode(): more existing code under a
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_PSCSI) case, as
sync/wide parameters only make sense for parallel SCSI.
For (SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_FC) and
(SCSIPI_BUSTYPE_SCSI, SCSIPI_BUSTYPE_SCSI_SAS), only print
tagged queing status if enabled. Just be silent for other
bustypes.

This change is prompted by this problem:
right now, FC (e.g. isp(4)) and SAS (e.g. mfi(4)) don't
do anything for ADAPTER_REQ_SET_XFER_MODE, and especially never
call scsipi_async_event(ASYNC_EVENT_XFER_MODE), so sd(4) always
runs untagged. Doing a scsipi_async_event(ASYNC_EVENT_XFER_MODE) with
appropriate parameters is enough to enable tagged queuing,
but then scsipi will print:
sd0: async, 8-bit transfers, tagged queueing
which is harmless (async, 8-bit transfers doens't make sense on SAS anyway)
but will confuse users. With this change scsipi will only print:
sd0: tagged queueing
which is correct.

In the long run, knowning the underlying transport in scsipi will
allow better handling of device which are not parallel SCSI.

Another change adding an extra callback to struct scsipi_bustype {}
will come (so that scsipi_print_xfer_mode(), which is SCSI-specific,
can be moved out of scsipi_base, and split into per-subtype callback),
but this will break kernel ABI and so is not suitable for
netbsd-6, so will be commmited later. The above is enough to get
tagged queuing on FC and SAS in netbsd-6.

/src/sys/compat/linux/arch/alpha/
H A Dlinux_syscall.h1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

H A Dlinux_sysent.c1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

1.67 Fri Apr 04 00:43:00 GMT 2008 njoly branches: 1.67.4; 1.67.6; 1.67.10; 1.67.12; 1.67.14;
Regen for linux_sys_msync removal.

/src/sys/compat/ultrix/
H A Dultrix_syscallargs.h1.67 Sat Jan 06 16:41:23 GMT 2018 kamil branches: 1.67.2; 1.67.4;
Revert vadvise(2) removal

This system call was used in legacy Lisp code, that was inherited to modern
age and still compiled against supported compat layers (e.g. in clisp,
oaklisp, Franz Lisp).

It used to instruct the kernel about paging policy (G/C aware, flush etc).

Newly compiled code (assuming that it will detect vadvise()) will use the
libc stub for vadvise(). The headers for this interface are gone.

vadvise(2) could be marked as COMPAT_80, but as long as we support ultrix,
sunos or aout68k ABI, don't bother with this.

Requested by <mrg>

1.67 Sat Jan 06 16:41:23 GMT 2018 kamil branches: 1.67.2; 1.67.4;
Revert vadvise(2) removal

This system call was used in legacy Lisp code, that was inherited to modern
age and still compiled against supported compat layers (e.g. in clisp,
oaklisp, Franz Lisp).

It used to instruct the kernel about paging policy (G/C aware, flush etc).

Newly compiled code (assuming that it will detect vadvise()) will use the
libc stub for vadvise(). The headers for this interface are gone.

vadvise(2) could be marked as COMPAT_80, but as long as we support ultrix,
sunos or aout68k ABI, don't bother with this.

Requested by <mrg>

1.67 Sat Jan 06 16:41:23 GMT 2018 kamil branches: 1.67.2; 1.67.4;
Revert vadvise(2) removal

This system call was used in legacy Lisp code, that was inherited to modern
age and still compiled against supported compat layers (e.g. in clisp,
oaklisp, Franz Lisp).

It used to instruct the kernel about paging policy (G/C aware, flush etc).

Newly compiled code (assuming that it will detect vadvise()) will use the
libc stub for vadvise(). The headers for this interface are gone.

vadvise(2) could be marked as COMPAT_80, but as long as we support ultrix,
sunos or aout68k ABI, don't bother with this.

Requested by <mrg>

/src/share/misc/
H A Dairport1.67 Fri Sep 15 19:20:11 GMT 2017 mbalmer branches: 1.67.4; 1.67.6;
Fix COC.

1.67 Fri Sep 15 19:20:11 GMT 2017 mbalmer branches: 1.67.4; 1.67.6;
Fix COC.

1.67 Fri Sep 15 19:20:11 GMT 2017 mbalmer branches: 1.67.4; 1.67.6;
Fix COC.

/src/sys/arch/x86/x86/
H A Dtsc.h1.7 Mon Jun 15 09:09:24 GMT 2020 msaitoh branches: 1.7.6;
Serialize rdtsc using with lfence, mfence or cpuid to read TSC more precisely.

x86/x86/tsc.c rev. 1.67 reduced cache problem and got big improvement, but it
still has room. I measured the effect of lfence, mfence, cpuid and rdtscp.
The impact to TSC skew and/or drift is:

AMD: mfence > rdtscp > cpuid > lfence-serialize > lfence = nomodify
Intel: lfence > rdtscp > cpuid > nomodify

So, mfence is the best on AMD and lfence is the best on Intel. If it has no
SSE2, we can use cpuid.

NOTE:
- An AMD's document says DE_CFG_LFENCE_SERIALIZE bit can be used for
serializing, but it's not so good.
- On Intel i386(not amd64), it seems the improvement is very little.
- rdtscp instruct can be used as serializing instruction + rdtsc, but
it's not good as [lm]fence. Both Intel and AMD's document say that
the latency of rdtscp is bigger than rdtsc, so I suspect the difference
of the result comes from it.

/src/sys/compat/sunos/
H A Dsyscalls.master1.67 Sun Mar 04 06:01:30 GMT 2007 christos branches: 1.67.16; 1.67.24; 1.67.28;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.
1.67 Sun Mar 04 06:01:30 GMT 2007 christos branches: 1.67.16; 1.67.24; 1.67.28;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.
1.67 Sun Mar 04 06:01:30 GMT 2007 christos branches: 1.67.16; 1.67.24; 1.67.28;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.
1.67 Sun Mar 04 06:01:30 GMT 2007 christos branches: 1.67.16; 1.67.24; 1.67.28;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.
/src/share/tmac/
H A Ddoc2html1.67 Tue Nov 22 00:36:49 GMT 2016 kamil branches: 1.67.6; 1.67.14; 1.67.16;
Add entry for pthread_dbg in share/tmac/doc2html

pthread_dbg is POSIX Debug Threads Library

Sponsored by <The NetBSD Foundation>

1.67 Tue Nov 22 00:36:49 GMT 2016 kamil branches: 1.67.6; 1.67.14; 1.67.16;
Add entry for pthread_dbg in share/tmac/doc2html

pthread_dbg is POSIX Debug Threads Library

Sponsored by <The NetBSD Foundation>

1.67 Tue Nov 22 00:36:49 GMT 2016 kamil branches: 1.67.6; 1.67.14; 1.67.16;
Add entry for pthread_dbg in share/tmac/doc2html

pthread_dbg is POSIX Debug Threads Library

Sponsored by <The NetBSD Foundation>

1.67 Tue Nov 22 00:36:49 GMT 2016 kamil branches: 1.67.6; 1.67.14; 1.67.16;
Add entry for pthread_dbg in share/tmac/doc2html

pthread_dbg is POSIX Debug Threads Library

Sponsored by <The NetBSD Foundation>

/src/sys/compat/linux/arch/m68k/
H A Dlinux_sysent.c1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
H A Dlinux_syscalls.c1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.
H A Dlinux_syscall.h1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.

1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.

1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.

1.67 Wed Jun 18 00:23:06 GMT 2008 tsutsui branches: 1.67.2; 1.67.4; 1.67.6;
Regen from syscalls.master rev 1.62:
> Include <sys/sched.h> before <sys/syscallargs.h> for cpuset_t.

/src/sys/arch/sparc64/conf/
H A DMakefile.sparc641.67 Sat Aug 30 13:23:55 GMT 2008 martin branches: 1.67.2; 1.67.4; 1.67.8; 1.67.10;
We are not creating a.out NMAGIC files, and handling the required alignement
of sections explicitly in the ldscript, so do not pass -n to ld.
This fixes the strange combined text/data sections seen with certain
(smaller) kernels as explained on tech-toolchain.
Found by Nick Hudson, ok: matthew green.

1.67 Sat Aug 30 13:23:55 GMT 2008 martin branches: 1.67.2; 1.67.4; 1.67.8; 1.67.10;
We are not creating a.out NMAGIC files, and handling the required alignement
of sections explicitly in the ldscript, so do not pass -n to ld.
This fixes the strange combined text/data sections seen with certain
(smaller) kernels as explained on tech-toolchain.
Found by Nick Hudson, ok: matthew green.

1.67 Sat Aug 30 13:23:55 GMT 2008 martin branches: 1.67.2; 1.67.4; 1.67.8; 1.67.10;
We are not creating a.out NMAGIC files, and handling the required alignement
of sections explicitly in the ldscript, so do not pass -n to ld.
This fixes the strange combined text/data sections seen with certain
(smaller) kernels as explained on tech-toolchain.
Found by Nick Hudson, ok: matthew green.

1.67 Sat Aug 30 13:23:55 GMT 2008 martin branches: 1.67.2; 1.67.4; 1.67.8; 1.67.10;
We are not creating a.out NMAGIC files, and handling the required alignement
of sections explicitly in the ldscript, so do not pass -n to ld.
This fixes the strange combined text/data sections seen with certain
(smaller) kernels as explained on tech-toolchain.
Found by Nick Hudson, ok: matthew green.

1.67 Sat Aug 30 13:23:55 GMT 2008 martin branches: 1.67.2; 1.67.4; 1.67.8; 1.67.10;
We are not creating a.out NMAGIC files, and handling the required alignement
of sections explicitly in the ldscript, so do not pass -n to ld.
This fixes the strange combined text/data sections seen with certain
(smaller) kernels as explained on tech-toolchain.
Found by Nick Hudson, ok: matthew green.

/src/sys/arch/hpcmips/conf/
H A DTX39121.67 Sat Aug 26 20:26:45 GMT 2006 christos branches: 1.67.6; 1.67.22; 1.67.32; 1.67.38;
PR/34283: Gene ENonymous: Add IPFILTER_LOOKUP to the default kernel options
Also remove CCITT,NS,NIP

1.67 Sat Aug 26 20:26:45 GMT 2006 christos branches: 1.67.6; 1.67.22; 1.67.32; 1.67.38;
PR/34283: Gene ENonymous: Add IPFILTER_LOOKUP to the default kernel options
Also remove CCITT,NS,NIP

1.67 Sat Aug 26 20:26:45 GMT 2006 christos branches: 1.67.6; 1.67.22; 1.67.32; 1.67.38;
PR/34283: Gene ENonymous: Add IPFILTER_LOOKUP to the default kernel options
Also remove CCITT,NS,NIP

1.67 Sat Aug 26 20:26:45 GMT 2006 christos branches: 1.67.6; 1.67.22; 1.67.32; 1.67.38;
PR/34283: Gene ENonymous: Add IPFILTER_LOOKUP to the default kernel options
Also remove CCITT,NS,NIP

1.67 Sat Aug 26 20:26:45 GMT 2006 christos branches: 1.67.6; 1.67.22; 1.67.32; 1.67.38;
PR/34283: Gene ENonymous: Add IPFILTER_LOOKUP to the default kernel options
Also remove CCITT,NS,NIP

/src/sys/arch/i386/include/
H A Dparam.h1.67 Thu Oct 18 15:28:37 GMT 2007 yamt branches: 1.67.16; 1.67.20; 1.67.28; 1.67.30;
merge yamt-x86pmap branch.

- reduce differences between amd64 and i386. notably, share pmap.c
between them. it makes several i386 pmap improvements available to
amd64, including tlb shootdown reduction and bug fixes from Stephan Uphoff.
- implement deferred pmap switching for amd64.
- remove LARGEPAGES option. always use large pages if available.
also, make it work on amd64.

1.67 Thu Oct 18 15:28:37 GMT 2007 yamt branches: 1.67.16; 1.67.20; 1.67.28; 1.67.30;
merge yamt-x86pmap branch.

- reduce differences between amd64 and i386. notably, share pmap.c
between them. it makes several i386 pmap improvements available to
amd64, including tlb shootdown reduction and bug fixes from Stephan Uphoff.
- implement deferred pmap switching for amd64.
- remove LARGEPAGES option. always use large pages if available.
also, make it work on amd64.

1.67 Thu Oct 18 15:28:37 GMT 2007 yamt branches: 1.67.16; 1.67.20; 1.67.28; 1.67.30;
merge yamt-x86pmap branch.

- reduce differences between amd64 and i386. notably, share pmap.c
between them. it makes several i386 pmap improvements available to
amd64, including tlb shootdown reduction and bug fixes from Stephan Uphoff.
- implement deferred pmap switching for amd64.
- remove LARGEPAGES option. always use large pages if available.
also, make it work on amd64.

1.67 Thu Oct 18 15:28:37 GMT 2007 yamt branches: 1.67.16; 1.67.20; 1.67.28; 1.67.30;
merge yamt-x86pmap branch.

- reduce differences between amd64 and i386. notably, share pmap.c
between them. it makes several i386 pmap improvements available to
amd64, including tlb shootdown reduction and bug fixes from Stephan Uphoff.
- implement deferred pmap switching for amd64.
- remove LARGEPAGES option. always use large pages if available.
also, make it work on amd64.

1.67 Thu Oct 18 15:28:37 GMT 2007 yamt branches: 1.67.16; 1.67.20; 1.67.28; 1.67.30;
merge yamt-x86pmap branch.

- reduce differences between amd64 and i386. notably, share pmap.c
between them. it makes several i386 pmap improvements available to
amd64, including tlb shootdown reduction and bug fixes from Stephan Uphoff.
- implement deferred pmap switching for amd64.
- remove LARGEPAGES option. always use large pages if available.
also, make it work on amd64.

/src/sys/arch/sparc64/sparc64/
H A Dintr.c1.67 Sat Aug 11 21:50:09 GMT 2012 mrg branches: 1.67.2; 1.67.16;
add an XXXSMP comment.

1.67 Sat Aug 11 21:50:09 GMT 2012 mrg branches: 1.67.2; 1.67.16;
add an XXXSMP comment.

1.67 Sat Aug 11 21:50:09 GMT 2012 mrg branches: 1.67.2; 1.67.16;
add an XXXSMP comment.

/src/sys/compat/linux32/arch/amd64/
H A Dlinux32_syscall.h1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

H A Dlinux32_syscallargs.h1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

H A Dlinux32_syscalls.c1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

H A Dlinux32_sysent.c1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

1.67 Fri Jul 13 18:21:45 GMT 2012 christos branches: 1.67.2; 1.67.4;
regen

/src/lib/libedit/
H A Dtty.c1.67 Mon Jan 01 22:32:46 GMT 2018 christos branches: 1.67.2; 1.67.4;
Only FLUSH if we are ending libedit; DRAIN if we suspend for readline.
This allows pasting multiline buffers (Gerry Swislow)

1.67 Mon Jan 01 22:32:46 GMT 2018 christos branches: 1.67.2; 1.67.4;
Only FLUSH if we are ending libedit; DRAIN if we suspend for readline.
This allows pasting multiline buffers (Gerry Swislow)

1.67 Mon Jan 01 22:32:46 GMT 2018 christos branches: 1.67.2; 1.67.4;
Only FLUSH if we are ending libedit; DRAIN if we suspend for readline.
This allows pasting multiline buffers (Gerry Swislow)

/src/distrib/sets/lists/comp/
H A Dmd.pmax1.67 Mon Dec 21 16:49:37 GMT 2015 christos branches: 1.67.14; 1.67.16;
Add fenv.h for mips.

1.67 Mon Dec 21 16:49:37 GMT 2015 christos branches: 1.67.14; 1.67.16;
Add fenv.h for mips.

1.67 Mon Dec 21 16:49:37 GMT 2015 christos branches: 1.67.14; 1.67.16;
Add fenv.h for mips.

Completed in 123 milliseconds

1234567891011>>