| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
|
|
| |
hold the kernel lock, but still need call one function that needs it.
Instead of grabbing the lock all over the place, move the locks into
the affected functions: trapsignal, scdebug*, ktrsyscall, ktrsysret,
systrace_redirect and ADDUPROF. In the cases we already hold the biglock
we'll just recurse.
kettenis@, beck@ ok
|
| |
|
|
|
|
|
| |
in master aborts. Return 0xffffffff to emulate what happens on non-perfect
architectures in that case.
ok deraadt@
|
| |
|
|
|
|
|
| |
in master aborts. Return 0xffffffff to emulate what happens on non-perfect
architectures in that case.
ok deraadt@
|
| |
|
|
|
|
|
| |
KERNEL_PROC_LOCK -> KERNEL_LOCK
KERNEL_PROC_UNLOCK -> KERNEL_UNLOCK
oga@ ok
|
| | |
|
| | |
|
| |
|
|
| |
Soon to be used by pyro(4) as well.
|
| |
|
|
| |
ok beck deraadt
|
| |
|
|
| |
link->bus->sc_dev.dv_unit.
|
| |
|
|
|
|
|
|
| |
problem has been tracked down. This fixes the sharing of the signal
handling state: shared bits go in sigacts, per-rthread bits goes in
struct proc.
ok deraadt@
|
| | |
|
| |
|
|
|
|
|
|
| |
The vm hackers don't use it, don't maintain it and have to look at it all the
time. About time this 800 lines of code hit /dev/null.
``never liked it'' tedu@. ariane@ was very happy when i told her i wrote
this diff.
|
| |
|
|
|
|
| |
spinning on a contended lock.
ok kettenis@
|
| |
|
|
|
|
| |
scsi?" rule, similar to how ethernet PHY drivers attach at mii.
Discussed on icb.
|
| |
|
|
|
|
|
| |
If it returns 1, skip calling the handlers further down the list. The
interrupt pin will remain asserted, and the handler will be called on the
next go-around. This makes sparc64 "similar" to other architectures.
ok kettenis jsing
|
| |
|
|
|
|
| |
This results in the higher IPL handlers being run first.
ok deraadt@ kettenis@
|
| |
|
|
|
| |
might need network (ie. nfs). Move the call to the MD boot() routines.
This cause for boot hangs diagnosed by kettenis.
|
| |
|
|
| |
to work fine on a t1k and a t5120, so let's enable this right from the start.
|
| |
|
|
|
|
| |
to the level they were at before we started splraise'ing for the various
handlers.
with jsing, ok kettenis
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
i386. Stop abusing it on other archs for controling a shutdown by
pressing the soft power button:
* Add a MI sysctl hw.allowpowerdown; if set to 1 (the default) it
allows a power button shutdown.
* Make acpi(4)/acpibtn(4) honor hw.allowpowerdown.
* Switch the various power button intercepts on landisk, sgi, sparc64
and zaurus over to hw.allowpowerdown.
* Garbage collect the machdep.kbdreset sysctl on all archs other than
amd64 and i386.
ok miod@
|
| |
|
|
|
|
|
| |
So let the intr_list_handler do this, and prevent the real handlers from doing
it as well.
tested by deraadt@
|
| |
|
|
|
|
|
| |
As discussed on icb: remove the comment,
remove pmap_remove (uvm_km_free does that for us).
ok oga@, deraadt@
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Allocating with M_WAITOK, checking for NULL, and calling panic() is
pointless (malloc() will panic if it can't allocate) so remove the check
and the call.
2) Allocating with M_WAITOK, checking for NULL, and then gracefully
handling failure to allocate is pointless. Instead also pass M_CANFAIL
so malloc() doesn't panic so we can actually handle it gracefully.
1) was done using Coccinelle.
Input from oga.
ok miod.
|
| |
|
|
|
|
|
|
|
| |
userland. Prevents userland applications from trapping forever on the next
floating point instruction executed after clearing this flag. Fixes issues
with threaded applications, sinc our pthreads library clears the FEF bit
under some circumstances.
ok miod@, tested by ajacoutot@
|
| |
|
|
|
|
|
| |
for now; that is unlikely to hit some of the remaining starvation bugs.
Repair the bufpages calculation too; i386 was doing it ahead of time
(incorrectly) and then re-calculating it.
ok thib
|
| |
|
|
|
|
|
|
|
| |
of silly flag twiddling code in various disk drivers.
ok deraadt@, miod@
N.B., users will need a -current disklabel(8) to be able to write new
disklabels to disk now.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new world order of pmemrange makes this data completely redundant
(being dealt with by the pmemrange constraints instead). Remove all code
that messes with the freelist.
While touching every caller of uvm_page_physload() anyway, add the flags
argument to all callers (all but one is 0 and that one already used
PHYSLOAD_DEVICE) and remove the macro magic to allow callers to continue
without it.
Should shrink the code a bit, as well.
matthew@ pointed out some mistakes i'd made.
``freelist death, I like. Ok.' ariane@
`I agree with the general direction, go ahead and i'll fix any fallout
shortly'' miod@ (68k 88k and vax i could not check would build)
|
| |
|
|
|
|
|
| |
Doesn't matter much since C++ ABI used by GCC doesn't mangle variable
names; however technically is required by Section 7.5 of the C++ spec.
Discussed with/OK guenther@, matthew@.
|
| |
|
|
|
|
|
| |
ATAPI devices. atapiscsi(4) is only for handling ATAPI devices on an
ATA bus, so umass(4) shouldn't care about it.
ok krw@, dlg@; no objections from deraadt@
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
returns EFBIG. This cannot be recovered from and is usually indicative
of a damaged pmap. Therefor, panic right here instead.
This diff meant the difference between dropping into single-user mode versus
getting a traceable panic.
ok kettenis@
|
| |
|
|
|
|
|
|
| |
zeroed out.
Documented this in code and updated PMAP_PREFER_* macros to use the corrected
values.
Discussed with and ok miod@
|
| |
|
|
| |
while there fix PMAP_PREFER_OFFSET() for good too, after discussion with ariane@
|
| | |
|
| |
|
|
|
|
| |
Enables future uvm_map code to make intelligent decisions during allocation.
No functional change.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
if you boot from a disk that ends up behind mpath(4) on sparc64,
it wont be able to resolve it to the actual disk device since a
path driver (eg sym(4)) sits where ofw tells us a disk is.
this diff allows the bootpath code to match on path drivers, and
then asks mpath to swap the path for the disk device.
ok kettenis@
|
| |
|
|
|
|
| |
Therefore set UVM_FLAG_FIXED and enforce this.
ok oga@
|
| | |
|
| |
|
|
| |
not reviewed yet, but it's better to track changes in cvs
|
| | |
|
| |
|
|
|
|
| |
until they're zombies and then send them signals (for intr mounts). Until
that is untangled, the sigacts change is unsafe. sthen@ was the victim
for this one
|
| |
|
|
|
| |
what the previous IO was. Less chance of copy and paste errors.
Suggested by miod@.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
are past. Use CLR() and SET() to modify necessary flags while leaving
the flags used by the buffer cache in peace.
Should make bufcache code much less confused about the state of the
bufs used in reading/writing disklabels. Other such flag abuses no
doubt await a visit.
Errors in original diff found by miod@.
ok beck@ deraadt@
|