Remove KDIR=, since SYS_INCLUDE=symlinks and KDIR are not supported any more.

branches: 1.1.2; 1.1.4; 1.1.6;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9).

branches: 1.8.32; 1.8.38;
Add #include <sys/simplelock.h>

branches: 1.7.4;
Match the docs: MUTEX_DRIVER/SPIN are now only for porting code written
for Solaris.

branches: 1.6.6; 1.6.8; 1.6.14; 1.6.16;
Merge some of the less invasive changes from the vmlocking branch:

- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements

branches: 1.5.18; 1.5.60; 1.5.62;
In dmover_backend_alloc(), make sure we get ninputs from the best_algdesc,
not just the most recent algdesc (which might be NULL).

Mmmm... LOCKDEBUG...
Change from unlock -> modify -> unlock to _lock_ -> modify -> unlock.

Fix typo.

branches: 1.2.2; 1.2.4; 1.2.6;
Grr, fix typo in RCS ID tag.

dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Introduce PR_ZERO to avoid open-coding memset()s everywhere. OK riastradh@.

branches: 1.45.4;
add fo_name so we can identify the fileops in a simple way.

include "ioconf.h" to get the 'void <driver>attach(int count);' prototype.

branches: 1.43.4;
Add d_discard to all struct cdevsw instances I could find.

All have been set to "nodiscard"; some should get a real implementation.

branches: 1.42.2;
Change (mostly mechanically) every cdevsw/bdevsw I can find to use
designated initializers.

I have not built every extant kernel so I have probably broken at
least one build; however I've also found and fixed some wrong
cdevsw/bdevsw entries so even if so I think we come out ahead.

Clear struct stat correctly. Fixes PR#46373.

branches: 1.40.4; 1.40.14; 1.40.18;
Modernize simple_lock() and ltsleep() usage in dmover(4).
(Thanks to rmind for providing hints on what was necessary.)

branches: 1.39.2;
dmover(4) really uses uvm(9). (Wasn't revealed by i386/ALL...)

Don't pull in the whole uvm(9) API to access only PAGE_SIZE and
some other constants. These are provided by sys/param.h now.

branches: 1.37.4;
If a multithreaded app closes an fd while another thread is blocked in
read/write/accept, then the expectation is that the blocked thread will
exit and the close complete.
Since only one fd is affected, but many fd can refer to the same file,
the close code can only request the fs code unblock with ERESTART.
Fixed for pipes and sockets, ERESTART will only be generated after such
a close - so there should be no change for other programs.
Also rename fo_abort() to fo_restart() (this used to be fo_drain()).
Fixes PR/26567

Rename fo_drain() to fo_abort(), 'drain' is used to mean 'wait for output
do drain' in many places, whereas fo_drain() was called in order to force
blocking read()/write() etc calls to return to userspace so that a close()
call from a different thread can complete.
In the sockets code comment out the broken code in the inner function,
it was being called from compat code.

compile again.

Fix locking as Andy explained. Also fill in uid and gid like sys_pipe did.

Fix PR/37878 and PR/37550: Provide stat(2) for all devices and don't use
fbadop_stat.

Add fileops::fo_drain(), to be called from fd_close() when there is more
than one active reference to a file descriptor. It should dislodge threads
sleeping while holding a reference to the descriptor. Implemented only for
sockets but should be extended to pipes, fifos, etc.

Fixes the case of a multithreaded process doing something like the
following, which would have hung until the process got a signal.

thr0 accept(fd, ...)
thr1 close(fd)

branches: 1.31.4; 1.31.12; 1.31.14; 1.31.18;
Update dmover fileops to compile again. From he@.

Welcome to 4.99.55:

- Add a lot of missing selinit() and seldestroy() calls.

- Merge selwakeup() and selnotify() calls into a single selnotify().

- Add an additional 'events' argument to selnotify() call. It will
indicate which event (POLL_IN, POLL_OUT, etc) happen. If unknown,
zero may be used.

Note: please pass appropriate value of 'events' where possible.
Proposed on: <tech-kern>

branches: 1.29.2; 1.29.6;
Start detangling lock.h from intr.h. This is likely to cause short term
breakage, but the mess of dependencies has been regularly breaking the
build recently anyhow.

branches: 1.28.4; 1.28.10;
Use selinit() / seldestroy().

branches: 1.27.6; 1.27.8; 1.27.10;
Implementation of per-CPU work-queues support for workqueue(9) interface.
WQ_PERCPU flag for workqueue and additional argument for workqueue_enqueue()
to assign a CPU might be used. Notes:
- For now, the list is used for workqueue_queue, which is non-optimal,
and will be changed with array, where index would be CPU ID.
- The data structures should be changed to be cache-friendly.

Reviewed by: <yamt>, <tech-kern>

Pass an ipl argument to pool_init/POOL_INIT to be used when initializing
the pool's lock.

branches: 1.25.2; 1.25.6;
Complete initializers so those files compile.

merge yamt-splraiseipl branch.

- finish implementing splraiseipl (and makeiplcookie).
http://mail-index.NetBSD.org/tech-kern/2006/07/01/0000.html
- complete workqueue(9) and fix its ipl problem, which is reported
to cause audio skipping.
- fix netbt (at least compilation problems) for some ports.
- fix PR/33218.

branches: 1.23.4; 1.23.6;
Correct first arg to falloc().

integrate kauth.

branches: 1.21.2; 1.21.4; 1.21.6;
merge yamt-uio_vmspace branch.

- use vmspace rather than proc or lwp where appropriate.
the latter is more natural to specify an address space.
(and less likely to be abused for random purposes.)
- fix a swdmover race.

branches: 1.20.2; 1.20.4;
dmoverioopen: add a missing simple_lock_init().

branches: 1.19.2;
Remove leading __ from __(const|inline|signed|volatile) -- it is obsolete.

merge ktrace-lwp.

branches: 1.17.6;
pass the flag to fdclone.

branches: 1.16.4; 1.16.6;
Correct a typo: it's fnullop_kqfilter and not fnullop_kqueue.

Cloning cleanup:
1. make fileops const
2. add 2 new negative errno's to `officially' support the cloning hack:
- EDUPFD (used to overload ENODEV)
- EMOVEFD (used to overload ENXIO)
3. Created an fdclone() function to encapsulate the operations needed for
EMOVEFD, and made all cloners use it.
4. Centralize the local noop/badop fileops functions to:
fnullop_fcntl, fnullop_poll, fnullop_kqfilter, fbadop_stat

Fix the fcntl entry points; cmd is a command, not the flags themselves.
Pointed out by Christos (he wrote the broken code originally, and I copied
it to another file later :-)

branches: 1.13.4;
move dupfd from struct proc to struct lwp - it's per-LWP, not per-process; we
use curlwp where the lwp is not directly available, i.e. in device open
routines

briefly discussed on tech-kern

Add immediate value support for dmoverio transactions.

branches: 1.11.2;
Back out the lwp/ktrace changes. They contained a lot of colateral damage,
and need to be examined and discussed more.

Pass lwp pointers throughtout the kernel, as required, so that the lwpid can
be inserted into ktrace records. The general change has been to replace
"struct proc *" with "struct lwp *" in various function prototypes, pass
the lwp through and use l_proc to get the process pointer when needed.

Bump the kernel rev up to 1.6V

In dmio_read(), make sure to set DMIO_STATE_READ_WAIT in ds->ds_flags
before going to sleep.

Change 'data' argument to fo_ioctl and fo_fcntl from 'caddr_t' to 'void *'.
Avoids a lot of casting and removes the need for some line breaks.
Removed a load of (caddr_t) casts from calls to copyin/copyout as well.
(approved by christos - he has a plan to remove caddr_t...)

Fix signed/unsigned comparison warnings.

merge kqueue branch into -current

kqueue provides a stateful and efficient event notification framework
currently supported events include socket, file, directory, fifo,
pipe, tty and device changes, and monitoring of processes and signals

kqueue is supported by all writable filesystems in NetBSD tree
(with exception of Coda) and all device drivers supporting poll(2)

based on work done by Jonathan Lemon for FreeBSD
initial NetBSD port done by Luke Mewburn and Jason Thorpe

Merge the gehenna-devsw branch into the trunk.

This merge changes the device switch tables from static array to
dynamically generated by config(8).

- All device switches is defined as a constant structure in device drivers.

- The new grammer ``device-major'' is introduced to ``files''.

device-major <prefix> char <num> [block <num>] [<rules>]

- All device major numbers must be listed up in port dependent majors.<arch>
by using this grammer.

- Added the new naming convention.
The name of the device switch must be <prefix>_[bc]devsw for auto-generation
of device switch tables.

- The backward compatibility of loading block/character device
switch by LKM framework is broken. This is necessary to convert
from block/character device major to device name in runtime and vice versa.

- The restriction to assign device major by LKM is completely removed.
We don't need to reserve LKM entries for dynamic loading of device switch.

- In compile time, device major numbers list is packed into the kernel and
the LKM framework will refer it to assign device major number dynamically.

branches: 1.4.2; 1.4.4; 1.4.6;
*Actually return* EINVAL when the output stream UIO's I/O is larger
than SSIZE_MAX.

Fix a signed/unsigned botch that broke an error recovery path.
(I could have sworn I fixed this bug over a week ago...)

Grr, fix typo in RCS ID tag.

dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Add some #includes to make a few more header files compile.

branches: 1.3.120;
merge ktrace-lwp.

Add immediate value support for dmoverio transactions.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.12;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Fix various typos, mainly in comments:
s/invaid/invalid/
s/instad/instead/
s/wich/with/
s/tranform/transform/
s/tranmist/transmit/
s/tranceiver/transceiver/
s/Tranparent/Transparent/
s/tranlated/translated/
s/tranfer/transfer/
s/tranmissions/transmissions/
s/condtions/conditions/
s/Recient/Recent/

Convert simplelock to mutex in this portion of dmover(4).

branches: 1.4.32; 1.4.38;
Add #include <sys/simplelock.h>

branches: 1.3.4; 1.3.10;
Use the softint API.

branches: 1.2.18; 1.2.60; 1.2.74; 1.2.76; 1.2.78;
Don't require that input buffers and output buffers be of the same
type.

branches: 1.1.2; 1.1.4; 1.1.6;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9).

branches: 1.7.32; 1.7.38;
Start detangling lock.h from intr.h. This is likely to cause short term
breakage, but the mess of dependencies has been regularly breaking the
build recently anyhow.

branches: 1.6.6;
Ensure that the 'pc' local variable is initialized, so that this builds again.

pesky missing semicolons.

- Make it compile again.
- Don't call pool_cache_init with a held simplelock.

Merge from vmlocking:

- pool_cache changes.
- Debugger/procfs locking fixes.
- Other minor changes.

branches: 1.2.12; 1.2.14; 1.2.18; 1.2.20;
Pass an ipl argument to pool_init/POOL_INIT to be used when initializing
the pool's lock.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.28; 1.1.66; 1.1.70;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9).

branches: 1.5.32; 1.5.38;
Start detangling lock.h from intr.h. This is likely to cause short term
breakage, but the mess of dependencies has been regularly breaking the
build recently anyhow.

branches: 1.4.12; 1.4.18; 1.4.24;
Pass an ipl argument to pool_init/POOL_INIT to be used when initializing
the pool's lock.

branches: 1.3.26; 1.3.30; 1.3.32;
merge ktrace-lwp.

branches: 1.2.4;
nuke trailing whitespace

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.12; 1.1.20; 1.1.22;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

merge ktrace-lwp.

Add a well-known dmover function name for the CRC32C used by the iSCSI
protocol.

branches: 1.3.2; 1.3.4; 1.3.6; 1.3.12;
Add standard names for 5-, 6-, 7-, and 8-way XOR.

Add "xor2", "xor3", and "xor4" function names, which perform an
XOR on 2, 3, and 4 input streams, respectively.

dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

fix a/an grammar in obvious cases

branches: 1.10.202;
Remove leading __ from __(const|inline|signed|volatile) -- it is obsolete.

merge ktrace-lwp.

branches: 1.8.16;
Go ahead and define xor function names up to xor16.

Add a well-known dmover function name for the CRC32C used by the iSCSI
protocol.

Add immediate value support for dmoverio transactions.

branches: 1.5.2;
Fix typo in previous.

Separate out the immediate value from the input buffer. The immediate
value field can now always be used as an input, and output, or both.

This is especially handy for data movers which can e.g. calculate the
CRC32C of a buffer as it is moved (which requires both a seed [input],
and a place to stash the result [output]).

branches: 1.3.2; 1.3.4; 1.3.6;
Add standard names for 5-, 6-, 7-, and 8-way XOR.

Add "xor2", "xor3", and "xor4" function names, which perform an
XOR on 2, 3, and 4 input streams, respectively.

dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

branches: 1.1.2; 1.1.4; 1.1.6;
dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.

kill alloca in favor of ssp

branches: 1.13.2;
include "ioconf.h" to get the 'void <driver>attach(int count);' prototype.

branches: 1.12.54; 1.12.74;
Start detangling lock.h from intr.h. This is likely to cause short term
breakage, but the mess of dependencies has been regularly breaking the
build recently anyhow.

branches: 1.11.8; 1.11.14; 1.11.20;
Make a minimal adaption to the new kthread_create() signature
by renaming swdmover_proc to swdmover_lwp, and pass in
&swdmover_backend as an argument to be used by the kthread.
Reviewed by ad@.

Merge some of the less invasive changes from the vmlocking branch:

- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements

branches: 1.9.30; 1.9.32;
merge ktrace-lwp.

branches: 1.8.4;
nuke trailing whitespace

branches: 1.7.8; 1.7.10;
Fix another used-before-initialized bug that gcc uncovered.

Add support for xor2-xor8 to swdmover.

Add a software implementation of the iSCSI CRC32C algorithm. This
serves as an example of how the immediate value can be used by a
dmover function.

branches: 1.4.2;
For functions with inputs and outputs, we currently require that the
buffer types be the same; don't rely on the middle-end to enforce this
for us.

Error out if we get an unexpected buffer type.

branches: 1.2.2; 1.2.4; 1.2.6;
Grr, fix typo in RCS ID tag.

dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.