Commit graph

12 commits

Author SHA1 Message Date
cinap_lenrek 27445c5768 kernel: cleanup qlock.c to use nil instead of 0 for pointers 2015-08-02 05:36:35 +02:00
cinap_lenrek 91614f582f kernel: dont use atomic increment for Proc.nlocks, maintain Lock.m for lock(), use uintptr intstead of long for pc values
change Proc.nlocks from Ref to int and just use normal increment and decrelemt
as done in erik quanstros 9atom.

It is not clear why we used atomic increment in the fist place as even if we
get preempted by interrupt and scheduled before we write back the incremented
value, it shouldnt be a problem and we'll just continue where we left off as
our process is the only one that can write to it.

Yoann Padioleau found that the Mach pointer Lock.m wasnt maintained
consistently for lock() vs canlock() and ilock(). Fixed.

Use uintptr instead of ulong for maxlockpc, maxilockpc and ilockpc debug variables.
2014-06-05 21:54:32 +02:00
cinap_lenrek a2d96d47c9 kernel: always reset notepending in eqlock, handle forceclosefgrp in eqlocks 2014-04-29 21:17:07 +02:00
cinap_lenrek 73b7f5f12c panic: trailing newlines 2012-03-28 18:13:45 +02:00
cinap_lenrek 3599f733ee more checking for eqlock 2012-02-05 20:52:12 +01:00
cinap_lenrek 413ab7785f eqlock: cleanup 2012-01-15 14:31:53 +01:00
cinap_lenrek 85fd5bf58d eqlock: dont rely on notepending flag when detecting eqlock interruption 2012-01-09 21:18:03 +01:00
cinap_lenrek 4c05d129e2 eqlock: fix postnote/qunlock race 2011-11-02 21:39:30 +01:00
cinap_lenrek e9d441fccf eqlock(): use separate lock to protect eql, fix missing unlock 2011-08-11 23:02:48 +02:00
cinap_lenrek 70e4b8d1f9 added eqlock(), a interruptable version of qlock. addresses issue #81 2011-08-10 16:21:17 +02:00
Taru Karttunen a9060cc06b Import sources from 2011-03-30 iso image - lib 2011-03-30 19:35:09 +03:00
Taru Karttunen e5888a1ffd Import sources from 2011-03-30 iso image 2011-03-30 15:46:40 +03:00