#
3745c395 |
| 21-Oct-2007 |
Julian Elischer <julian@FreeBSD.org> |
Rename the kthread_xxx (e.g. kthread_create()) calls to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it t
Rename the kthread_xxx (e.g. kthread_create()) calls to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first.
I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
show more ...
|
#
982d11f8 |
| 05-Jun-2007 |
Jeff Roberson <jeff@FreeBSD.org> |
Commit 14/14 of sched_lock decomposition. - Use thread_lock() rather than sched_lock for per-thread scheduling sychronization. - Use the per-process spinlock rather than the sched_lock for per-p
Commit 14/14 of sched_lock decomposition. - Use thread_lock() rather than sched_lock for per-thread scheduling sychronization. - Use the per-process spinlock rather than the sched_lock for per-process scheduling synchronization.
Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each)
show more ...
|
#
0c14ff0e |
| 04-Mar-2007 |
Robert Watson <rwatson@FreeBSD.org> |
Remove 'MPSAFE' annotations from the comments above most system calls: all system calls now enter without Giant held, and then in some cases, acquire Giant explicitly.
Remove a number of other MPSAF
Remove 'MPSAFE' annotations from the comments above most system calls: all system calls now enter without Giant held, and then in some cases, acquire Giant explicitly.
Remove a number of other MPSAFE annotations in the credential code and tweak one or two other adjacent comments.
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
acd3428b |
| 06-Nov-2006 |
Robert Watson <rwatson@FreeBSD.org> |
Sweep kernel replacing suser(9) calls with priv(9) calls, assigning specific privilege names to a broad range of privileges. These may require some future tweaking.
Sponsored by: nCircle
Sweep kernel replacing suser(9) calls with priv(9) calls, assigning specific privilege names to a broad range of privileges. These may require some future tweaking.
Sponsored by: nCircle Network Security, Inc. Obtained from: TrustedBSD Project Discussed on: arch@ Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri, Alex Lyashkov <umka at sevcity dot net>, Skip Ford <skip dot ford at verizon dot net>, Antoine Brodin <antoine dot brodin at laposte dot net>
show more ...
|
#
aed55708 |
| 22-Oct-2006 |
Robert Watson <rwatson@FreeBSD.org> |
Complete break-out of sys/sys/mac.h into sys/security/mac/mac_framework.h begun with a repo-copy of mac.h to mac_framework.h. sys/mac.h now contains the userspace and user<->kernel API and definitio
Complete break-out of sys/sys/mac.h into sys/security/mac/mac_framework.h begun with a repo-copy of mac.h to mac_framework.h. sys/mac.h now contains the userspace and user<->kernel API and definitions, with all in-kernel interfaces moved to mac_framework.h, which is now included across most of the kernel instead.
This change is the first step in a larger cleanup and sweep of MAC Framework interfaces in the kernel, and will not be MFC'd.
Obtained from: TrustedBSD Project Sponsored by: SPARTA
show more ...
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0 |
|
#
0909f38a |
| 10-Apr-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
On shutdown try to turn off all swap devices. This way GEOM providers are properly closed on shutdown.
Requested by: ru Reviewed by: alc MFC after: 2 weeks
|
#
36a52c3c |
| 06-Feb-2006 |
Jeff Roberson <jeff@FreeBSD.org> |
- Add the global 'rebooting' variable that is used to detect when boot() has been called.
Sponsored by: Isilon Systems, Inc. MFC After: 1 week
|
Revision tags: release/6.0.0_cvs, release/6.0.0 |
|
#
3fafa27b |
| 22-Sep-2005 |
Stephan Uphoff <ups@FreeBSD.org> |
Don't pretend to be thread0 when calling sync(). It confuses the lock manager since in some places thread0 is then used for vnode locking while curthread is used for vnode unlocking.
Found by: Yahoo
Don't pretend to be thread0 when calling sync(). It confuses the lock manager since in some places thread0 is then used for vnode locking while curthread is used for vnode unlocking.
Found by: Yahoo! Reviewed by: ps@,jhb@ MFC after: 3 days
show more ...
|
#
d07f87a2 |
| 08-Sep-2005 |
Don Lewis <truckman@FreeBSD.org> |
Add a new struct buf flag bit, B_PERSISTENT, and use it to tag struct bufs that are persistently held by ext2fs. Ignore any buffers with this flag in the code in boot() that counts "busy" and dirty
Add a new struct buf flag bit, B_PERSISTENT, and use it to tag struct bufs that are persistently held by ext2fs. Ignore any buffers with this flag in the code in boot() that counts "busy" and dirty buffers and attempts to sync the dirty buffers, which is done before attempting to unmount all the file systems during shutdown.
This fixes the problem caused by any ext2fs file systems that are mounted at system shutdown time, which caused boot() to give up on a non-zero number of buffers and skip the call to vfs_unmountall(). This left all the mounted file systems in a dirty state and caused them to all require cleanup by fsck on reboot.
Move the two separate copies of the "busy" buffer test in boot() to a separate function.
Nuke the useless spl() stuff in the ext2fs ULCK_BUF() macro.
Bring the PRINT_BUF_FLAGS definition in sys/buf.h up to date with this and previous flag changes.
PR: kern/56675, kern/85163 Tested by: "Matthias Andree" matthias.andree at gmx.de Reviewed by: bde MFC after: 3 days
show more ...
|
Revision tags: release/5.4.0_cvs, release/5.4.0 |
|
#
0b581232 |
| 12-Apr-2005 |
Jeff Roberson <jeff@FreeBSD.org> |
- Remove unused include.
|
Revision tags: release/4.11.0_cvs, release/4.11.0 |
|
#
2fd32b93 |
| 30-Nov-2004 |
Nate Lawson <njl@FreeBSD.org> |
Replace a printf with a KASSERT that we are indeed running on the BSP.
|
#
f7ebc7ce |
| 08-Nov-2004 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Bind to cpu0 for boot() processing on all platforms again.
|
#
70ce93f4 |
| 07-Nov-2004 |
Nate Lawson <njl@FreeBSD.org> |
Add comments to clarify why we need to run shutdown code on the BSP, update an old comment about boot() being MI, and note that splhigh() no longer disables interrupts.
|
#
0de3e728 |
| 05-Nov-2004 |
Peter Wemm <peter@FreeBSD.org> |
Restrict the sched_bind to cpu 0 to i386 and amd64 for now. I forgot that alpha still doesn't use logical cpu id's.
|
#
20e25d7d |
| 05-Nov-2004 |
Peter Wemm <peter@FreeBSD.org> |
Bind to cpu0 for boot() processing. (Note this is reboot, not startup) This means we'll always call the event hooks, device_shutdown etc on the BSP and theoretically means we can de-cruftify the cpu_
Bind to cpu0 for boot() processing. (Note this is reboot, not startup) This means we'll always call the event hooks, device_shutdown etc on the BSP and theoretically means we can de-cruftify the cpu_reset_proxy stuff.
show more ...
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
#
c5690651 |
| 04-Nov-2004 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Remove buf->b_dev field.
|
#
37abb77f |
| 04-Oct-2004 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Change the perfectly precise message printf("No buffers busy after final sync"); to printf("All buffers synced."); in order to not leave the users wondering if there should be.
|
#
9923b511 |
| 02-Sep-2004 |
Scott Long <scottl@FreeBSD.org> |
Turn PREEMPTION into a kernel option. Make sure that it's defined if FULL_PREEMPTION is defined. Add a runtime warning to ULE if PREEMPTION is enabled (code inspired by the PREEMPTION warning in ke
Turn PREEMPTION into a kernel option. Make sure that it's defined if FULL_PREEMPTION is defined. Add a runtime warning to ULE if PREEMPTION is enabled (code inspired by the PREEMPTION warning in kern_switch.c). This is a possible MT5 candidate.
show more ...
|
#
0eac4495 |
| 29-Aug-2004 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Remove the HW_WDOG option; it serves no purpose.
MFC after: 3 days
|
#
55c45354 |
| 20-Aug-2004 |
John Baldwin <jhb@FreeBSD.org> |
Remove some dead code under a straggling APIC_IO #ifdef that I missed back before 5.2.
|
#
b6915bdb |
| 15-Aug-2004 |
Don Lewis <truckman@FreeBSD.org> |
Yet another tweak to the shutdown messages in boot():
Don't count busy buffers before the initial call to sync() and don't skip the initial sync() if no busy buffers were called. Always call s
Yet another tweak to the shutdown messages in boot():
Don't count busy buffers before the initial call to sync() and don't skip the initial sync() if no busy buffers were called. Always call sync() at least once if syncing is requested. This defers the "Syncing disks, buffers remaining..." message until after the initial sync() call and the first count of busy buffers. This backs out changes in kern_shutdown 1.162.
Print a different message when there are no busy buffers after the initial sync(), which is now the expected situation.
Print an additional message when syncing has completed successfully in the unusual situation where the work of syncing was done by boot().
Uppercase one message to make it consistent with all of the other kernel shutdown messages.
Discussed with: bde (in a much earlier form, prior to 1.162) Reviewed by: njl (in an earlier form)
show more ...
|
#
c8c216d5 |
| 10-Aug-2004 |
Nate Lawson <njl@FreeBSD.org> |
Skip the syncing disks loop if there are no dirty buffers. Remove a variable used to flag the initial printf.
Submitted by: truckman (earlier version)
|
#
b1c81391 |
| 30-Jul-2004 |
Nate Lawson <njl@FreeBSD.org> |
Minor message cleanup.
|
#
46e38ce8 |
| 21-Jul-2004 |
Robert Watson <rwatson@FreeBSD.org> |
Don't sync the file system on panic by default. This seems to basically work very infrequently, and often results in a compound panic which confuses debugging; locking/SMP have made the layering vio
Don't sync the file system on panic by default. This seems to basically work very infrequently, and often results in a compound panic which confuses debugging; locking/SMP have made the layering violation (and risks) of this more obvious over time.
Discussed with: green, bde, et al.
show more ...
|
#
3a63b92c |
| 19-Jul-2004 |
Julian Elischer <julian@FreeBSD.org> |
You always spot the typos after you have committed.. Start sentence with a Cap.
|