| Age | Commit message (Collapse) | Author |
|---|
|
got 'disk_change = 1;' to keep the DUID cache up to date in Feb.
2011. Bad krw@.
ok deraadt@
|
|
compiles and boots, so the identical sparc code must too!
ok deraadt@
|
|
Also use it wherever we configure the hardware to direct interrupts to the
right CPU.
|
|
comments
ok millert@
|
|
ok miod@
|
|
|
|
ok millert@ jasper@
|
|
handler that was running has finished.
ok miod@, guenther@
|
|
|
|
use atomic operations to operate on pm_stats.resident_count. Is it really
necessary to keep track of that for the kernel pmap?
|
|
PR_WAITOK flag to pmap_init and pass NULL as the pool allocator.
|
|
symbols in ASM
ok deraadt@ mpi@
|
|
ok deraadt@
|
|
|
|
|
|
|
|
Found the hardway by benoit@.
|
|
where appropriate. Noop for disks with 512-byte sectors. i.e. the
only kind currently allowed in softraid volumes. But starts laying
the groundwork to allow disks with other sector sizes.
ok jsing@
|
|
|
|
order problems.
|
|
"shared reference pointers".
srp allows concurrent access to a data structure by multiple cpus
while avoiding interlocking cpu opcodes. it manages its own reference
counts and the garbage collection of those data structure to avoid
use after frees.
internally srp is a twisted version of hazard pointers, which are
a relative of RCU.
jmatthew wrote the bulk of a hazard pointer implementation and
changed bpf to use it to allow mpsafe access to bpfilters. however,
at s2k15 we were trying to apply it to other data structures but
the memory overhead of every hazard pointer would have blown out
significantly in several uses cases. a bulk of our time at s2k15
was spent reworking hazard pointers into srp.
this diff adds the srp api and adds the necessary metadata to struct
cpuinfo on our MP architectures. srp on uniprocessor platforms has
alternate code that is optimised because it knows there'll be no
concurrent access to data by multiple cpus.
srp is made available to the system via param.h, so it should be
available everywhere in the kernel.
the docs likely need improvement cos im too close to the implementation.
ok mpi@
|
|
|
|
|
|
Note that pseudo-drivers not using if_input() are not affected by this
conversion.
ok mikeb@, kettenis@, claudio@, dlg@
|
|
|
|
miod pointed out that time_second should be compared to 1 not 0 in the
md resettodr() functions as it is initialised to 1.
ok miod@ deraadt@
|
|
ok deraadt@
|
|
interrupts at pckbc attach time, and get rid of the `intr_establish'
pckbc callback.
Tested on hppa (gsckbc) and sgi (pckbc@hpc); not tested on sparc64 (pckbc@ebus)
but this attachment was already behaving this way and its intr_establish
callback was an empty function.
|
|
not available to programs anyway.
|
|
the kernel_lock), as we already do better conversions in
user-mode. Yet, no need for every single driver to fiddle with the
conversion code as they are done transparently by common MI code. With
help from armani and miod, support from mpi
ok armani@
|
|
ok miod@
|
|
delete coredump_trad(), uvm_coredump(), cpu_coredump(), struct md_coredump,
and various #includes that are superfluous.
This leaves compat_linux processes without a coredump callback. If that
ability is desired, someone should update it to use coredump_elf32() and
verify the results...
ok kettenis@
|
|
had a proper stdint.h. No ports fallout. OK guenther@ miod@
|
|
unification...
|
|
there's no need to do it in m_devget(9).
Stop passing an ``ifp'' will help for upcoming interface pointer -> index
conversion.
While here remove unused ``ifp'' argument from m_clget(9) and kill two
birds^W layer violations in one commit.
ok henning@
|
|
for non-DIAGNOSTIC kernels.
ok deraadt@
|
|
pv lists with a mutex. Some minor code adjustments to prevent holding locks
too long. This should make pmap_enter(9), pmap_remove(9) and
pmap_page_protect(9) safe to use without holding the kernel lock.
|
|
when we call pmap_release(). Turn debug code into printf and remove the code
that tried to mop up. Override Debugger() such that it inserts a trap
instruction directly into the code such that we get useful backtraces.
This way I don't need to worry about pmap_release() removing pv entries when
making this pmap mpsafe.
|
|
|
|
|
|
|
|
they do "interesting" things with APIs i want to change, and i can't
find any evidence anyone uses them anymore. instead of burning time
on changes i cant test, ill take a chance that noone will miss them.
no objections from anyone
ok mpi@ deraadt@ henning@ sthen@
|
|
Our reset function did not reset the ring and LDC map and our stop function
did not reset the LDC channel state and the some of the ring state. Also
make sure we clear IFF_OACTIVE whenever we re-establish a connection on the
LDC channel. Finally, initialize the link state to LINK_STATE_DOWN such
that interfaces that have not been configured yet, don't show up as active.
This should improve the reliability of re-establishing network connections
between domains after some sort of hickup considerably.
|
|
This makes sure the other side correctly sees the channel being reset.
|
|
|
|
Use this on vax to correctly pick the end of the stack area now that the
stackgap adjustment code will no longer guarantee it is a fixed location.
|
|
|
|
|
|
sc_tx_cont and let them wrap around. Make sure we don't fill the last
descriptor on the ring such that we don't confuse a completely filled ring
with a completely empty one. Also make sure we don't post the same
descriptors twice.
|
|
|
