ed 2008-08-20 12:20:22 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
sys/sys kernel.h
Log:
SVN rev 181921 on 2008-08-20 12:20:22Z by ed
Remove the now unused `lbolt' variable from the kernel.
We used to have a single
rwatson 2008-07-30 18:28:09 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_7)
sys/kern kern_synch.c
Log:
SVN rev 181005 on 2008-07-30 18:28:09Z by rwatson
Merge r177272 from head to stable/7:
Consistently use ANSI C declarations for all
rwatson 2008-03-16 18:59:21 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Consistently use ANSI C declarationsfor all functions in kern_synch.c.
Revision ChangesPath
1.310 +7 -19 src/sys/kern/kern_synch.c
___
jeff2008-03-10 03:16:51 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
- Handle kdb switch panics outside of mi_switch() to remove some instructions
from the common path and make the code more clear. Whether this has any
impact o
jeff2007-10-08 23:40:40 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
- Restore historical yield() behavior by manually lowering priority and
switching.
Approved by:re
Revision ChangesPath
1.302 +6 -3 src
jhb 2007-02-27 18:46:07 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Print tid's rather than thread pointers in KTR_PROC traces.
Revision ChangesPath
1.289 +8 -8 src/sys/kern/kern_synch.c
__
jeff2007-01-03 02:38:41 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
- Fix schedgraph output with KSE threads. Call thread_switchout() after
calling CTR() so we don't confuse a new kse thread with a real preemption.
Revision C
In message <[EMAIL PROTECTED]>, Alexey Dokuchaev writes:
>On Thu, Nov 30, 2006 at 08:27:38AM +, Poul-Henning Kamp wrote:
>> phk 2006-11-30 08:27:38 UTC
>>
>> FreeBSD src repository
>>
>> Modified files:
>> sys/kern kern_synch.c
>> Log:
>> Only grab the sched_l
On Thu, Nov 30, 2006 at 08:27:38AM +, Poul-Henning Kamp wrote:
> phk 2006-11-30 08:27:38 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern kern_synch.c
> Log:
> Only grab the sched_lock if we actually need to modify the thread priority.
>
> Du
phk 2006-11-30 08:27:38 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Only grab the sched_lock if we actually need to modify the thread priority.
During a buildworld only 2/3 of the calls to msleep actually changed
the priority.
jhb 2006-11-15 20:44:07 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Adjust assertions to allow for magical properties of the 'lbolt' wait
channel for tsleep():
- Allow tsleep() on &lbolt without Giant with a timeout 0 since &lbolt has
davidxu 2006-06-15 06:41:57 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Use scheduler API sched_relinquish() to implement yield() syscall.
Revision ChangesPath
1.281 +2 -8 src/sys/kern/kern_synch.c
___
jhb 2006-06-03 20:49:44 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
In the case of reentering the debugger due to an attempt to perform a
context switch while in the debugger, reenter the debugger sooner before
performing any statisti
Jeff Roberson <[EMAIL PROTECTED]> writes:
> The api used to be mtx_enter(). It's nice to have consistent
> comments so we don't confuse new developers or non-native english
> speakers.
especially when "mtx_enter()" suggests the use of mutexes to protect
code, while the policy in FreeBSD is to use
On Wednesday 22 February 2006 15:58, Jeff Roberson wrote:
> On Wed, 22 Feb 2006, Colin Percival wrote:
>
> > John Baldwin wrote:
> >> Log:
> >> Fixup some comments. Mutexes's are locked, not entered for several years
> >
> > What's the difference? I thought "lock a mutex", "enter a mutex", a
On Wed, 22 Feb 2006, Colin Percival wrote:
John Baldwin wrote:
Log:
Fixup some comments. Mutexes's are locked, not entered for several years
What's the difference? I thought "lock a mutex", "enter a mutex", and "pick
up a lock" were all interchangeable.
The api used to be mtx_enter().
John Baldwin wrote:
> Log:
> Fixup some comments. Mutexes's are locked, not entered for several years
What's the difference? I thought "lock a mutex", "enter a mutex", and "pick
up a lock" were all interchangeable.
Colin Percival
___
cvs-all@freeb
jhb 2006-02-22 20:46:11 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
Fixup some comments. Mutexes's are locked, not entered for several years
now and msleep blocks threads rather than processes.
Revision ChangesPath
1.277
jhb 2005-12-29 21:15:32 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
patch(1) and I aren't friends today. Axe a duplicate copy of
the msleep_spin() function definition.
Spotted by: pjd
Revision ChangesPath
1.273
On Thursday 29 December 2005 03:57 pm, John Baldwin wrote:
> jhb 2005-12-29 20:57:45 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern kern_synch.c
> sys/sys systm.h
> Log:
> Add a new function msleep_spin() which is a slightly stripped d
jhb 2005-12-29 20:57:45 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
sys/sys systm.h
Log:
Add a new function msleep_spin() which is a slightly stripped down version
of msleep(). msleep_spin() doesn't support changing the pr
jhb 2005-12-05 20:14:57 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_5)
sys/kern kern_synch.c
Log:
MF6: Use >= rather than > to check for a process exceeding its time limit.
Revision ChangesPath
1.257.2.9 +2 -2 src/sys/kern/
jhb 2005-12-05 20:14:40 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_6)
sys/kern kern_synch.c
Log:
MFC: Use >= rather than > to check for a process exceeding its time limit.
Revision ChangesPath
1.270.2.1 +2 -2 src/sys/kern/
jhb 2005-11-28 19:09:08 UTC
FreeBSD src repository
Modified files:
sys/kern kern_synch.c
Log:
When checking to see if a process has exceeded its time limit, flag the
process as over the limit when its time is >= to the limit rather than >
the limit. Technical
24 matches
Mail list logo
