Commit Graph

8 Commits

Author SHA1 Message Date
jakllsch
3af888c194 Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9). 2011-05-14 18:24:47 +00:00
ad
0664a0459b 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.
2008-01-04 21:17:40 +00:00
he
5f195f5b4e Ensure that the 'pc' local variable is initialized, so that this builds again. 2007-11-12 15:50:21 +00:00
dogcow
c067a1b95c pesky missing semicolons. 2007-11-08 07:53:11 +00:00
ad
54221c3e0f - Make it compile again.
- Don't call pool_cache_init with a held simplelock.
2007-11-07 14:04:27 +00:00
ad
d18c6ca4de Merge from vmlocking:
- pool_cache changes.
- Debugger/procfs locking fixes.
- Other minor changes.
2007-11-07 00:23:13 +00:00
ad
59d979c5f1 Pass an ipl argument to pool_init/POOL_INIT to be used when initializing
the pool's lock.
2007-03-12 18:18:22 +00:00
thorpej
5d06c0e812 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.
2002-08-02 00:30:37 +00:00