the kernel enables interrupts and then sets up clocks. If we catch a timer
interrupt in between and call hardclock() we'll explode so for now just
bail when we get one while cold
- load uvm.page_idle_zero with "ldub" instead of "ld", avoiding an
unaligned access panic introduced since the int->bool changes.
now a -current kernel (both UP and MP) boot on my SS20 as long as
i have "options LOCKDEBUG" as well.
the kernel enables interrupts and then sets up clocks. If we catch a timer
interrupt in between and call hardclock() we'll explode so for now just
bail when we get one while cold
with newlock2 merge:
Replace the Mach-derived boolean_t type with the C99 bool type. A
future commit will replace use of TRUE and FALSE with true and false.
int _bus_dmatag_subregion(bus_dma_tag_t tag,
bus_addr_t min_addr,
bus_addr_t max_addr,
bus_dma_tag_t *newtag,
int flags)
void _bus_dmatag_destroy(bus_dma_tag_t tag)
that allow a (normally broken/limited) device to restrict the bus address
range it can talk to. this is used by bce(4) to limit DMA addresses to
1GB range, the maximum the chip can address.
all this is from Yorick Hardy <yhardy@uj.ac.za> with input from several
people on tech-kern.
XXX: bus_dma(9) needs an update still.
P_*/L_* naming convention, and rename the in-kernel flags to avoid
conflict. (P_ -> PK_, L_ -> LW_ ). Add back the (now unused) LSDEAD
constant.
Restores source compatibility with pre-newlock2 tools like ps or top.
Reviewed by Andrew Doran.
already released the lock when we reach the waiters check.
- mutex_enter(): denote the start and end of the critical and export
labels. If an LWP is preempted after grabbing the interlock, the dummy
owner value (0xff000000) will persist, but the real owner value must be
set soon to prevent deadlock. On entry to interrupt we'll need to check
for this and set in the correct value if the LWP was interrupted in the
critical section.
debugging and its main use is in device drivers. Its used there to signal
that the flagged buffer has a special meaning or should be handled
differently.
OK'd by Bill Sudenmund on tech-kern.
console keyboard and mouse on them.
We are not there yet because currently both wsdisplay and zstty assume
that they are the console. On sun-4, zstty wins because it attaches
last and overwrites the console device that wscons had set previously.
