#
272461 |
|
02-Oct-2014 |
gjb |
Copy stable/10@r272459 to releng/10.1 as part of the 10.1-RELEASE process.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
227537 |
|
15-Nov-2011 |
marius |
As it turns out, r186347 actually is insufficient to avoid the use of the curthread-accessing part of mtx_{,un}lock(9) when using a r210623-style curthread implementation on sparc64, crashing the kernel in its early cycles as PCPU isn't set up, yet (and can't be set up as OFW is one of the things we need for that, which leads to a chicken-and-egg problem). What happens is that due to the fact that the idea of r210623 actually is to allow the compiler to cache invocations of curthread, it factors out obtaining curthread needed for both mtx_lock(9) and mtx_unlock(9) to before the branch based on kobj_mutex_inited when compiling the kernel without the debugging options. So change kobj_class_compile_static(9) to just never acquire kobj_mtx, effectively restricting it to its documented use, and add a kobj_init_static(9) for initializing objects using a class compiled with the former and that also avoids using mutex(9) (and malloc(9)). Also assert in both of these functions that they are used in their intended way only. While at it, inline kobj_register_method() and kobj_unregister_method() as there wasn't much point for factoring them out in the first place and so that a reader of the code has to figure out the locking for fewer functions missing a KOBJ_ASSERT. Tested on powerpc{,64} by andreast.
Reviewed by: nwhitehorn (earlier version), jhb MFC after: 3 days
|
#
163733 |
|
28-Oct-2006 |
maxim |
o Fix incorrect function name (kobj_free -> kobj_delete).
Obtained from: DragonFlyBSD MFC after: 1 week
|
#
147647 |
|
28-Jun-2005 |
hmp |
Use 'manual page' instead of 'man page' for consistency.
Approved by: re (hrs)
|
#
131530 |
|
03-Jul-2004 |
ru |
Mechanically kill hard sentence breaks and double whitespaces.
|
#
123345 |
|
09-Dec-2003 |
mtm |
Grammar
|
#
115440 |
|
31-May-2003 |
hmp |
Some mdoc(7) fixes:
Nuke incorrect usage of .Ar; replace it with .Vt, .Va or .Fa appropriately. The .Ar mdoc(7) specifier should only be used when displaying command line arguments.
Approved by: des (mentor)
|
#
88509 |
|
26-Dec-2001 |
davidc |
Update function definitions and required include files to reflect the current state of the system.
Approved by: alfred
|
#
84306 |
|
01-Oct-2001 |
ru |
mdoc(7) police: Use the new .In macro for #include statements.
|
#
79727 |
|
14-Jul-2001 |
schweikh |
Removed whitespace at end-of-line; no content changes. I simply did cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//'
BTW, what editors are the culprits? I'm using vim and it shows me whitespace at EOL in troff files with a thick blue block...
Reviewed by: Silence from cvs diff -b MFC after: 7 days
|
#
79538 |
|
10-Jul-2001 |
ru |
mdoc(7) police: removed HISTORY info from the .Os call.
|
#
79454 |
|
09-Jul-2001 |
dd |
mdoc(7) police: remove extraneous .Pp before and/or after .Sh.
|
#
75664 |
|
18-Apr-2001 |
ru |
mdoc(7) police: use .Fx.
|
#
65174 |
|
28-Aug-2000 |
dfr |
Document kobj_class_compile_static().
|
#
60391 |
|
11-May-2000 |
bde |
Removed bogus quoting of single tokens in a .Fn invocation. This helps my synopsis checker decide which .Fn's are for prototypes (most function parameters require quoting because they have multiple tokens).
|
#
60280 |
|
09-May-2000 |
mpp |
Spelling fix: despatching -> dispatching. This makes the spelling consistent throughout the man page.
PR: docs/18467 Submitted by: Alexander N. Kabaev <ak03@gte.com>
|
#
59626 |
|
25-Apr-2000 |
wollman |
Add punctuation to make a sentence more readable.
|
#
59116 |
|
10-Apr-2000 |
dfr |
Use the existing Fx macros for rendering "FreeBSD ver".
Submitted by: Sheldon Hearn <sheldonh@uunet.co.za>
|
#
59092 |
|
08-Apr-2000 |
dfr |
Add manpage for kernel object system.
|