[Kos-cvs] kos ChangeLog,1.49,1.50

[thomas at kos.enix.org]

Update of /home/kos/cvs/kos
In directory the-doors:/tmp/cvs-serv8985

Modified Files:
	ChangeLog 
Log Message:
2005-01-04  Thomas Petazzoni  <thomas at crazy.kos.nx>

	* modules/test/sem_test.c: Added a test that is similar to the
	mutex one. Instead of using the semaphore as a synchronisation
	primitive, we use it as a mutual exclusion primitive.

	* modules/test/mutex_test.c: Added some usleep() to make sure
	interrupts are generated inside the critical section.

	* modules/kitc/_kmutex.c: doxygen-aware comments.
	(kmutex_lock, kmutex_unlock): Make sure that a mutex that has just
	been released cannot be stolen by an other thread but the one that
	has been woken up. Solution inspired from SOS implementation of
	mutexes.




Index: ChangeLog
===================================================================
RCS file: /home/kos/cvs/kos/ChangeLog,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- ChangeLog	29 Dec 2004 19:28:49 -0000	1.49
+++ ChangeLog	4 Jan 2005 21:57:50 -0000	1.50
@@ -1,3 +1,18 @@
+2005-01-04  Thomas Petazzoni  <thomas at crazy.kos.nx>
+
+	* modules/test/sem_test.c: Added a test that is similar to the
+	mutex one. Instead of using the semaphore as a synchronisation
+	primitive, we use it as a mutual exclusion primitive.
+
+	* modules/test/mutex_test.c: Added some usleep() to make sure
+	interrupts are generated inside the critical section.
+
+	* modules/kitc/_kmutex.c: doxygen-aware comments.
+	(kmutex_lock, kmutex_unlock): Make sure that a mutex that has just
+	been released cannot be stolen by an other thread but the one that
+	has been woken up. Solution inspired from SOS implementation of
+	mutexes.
+
 2004-12-29  Thomas Petazzoni  <thomas at crazy.kos.nx>
 
 	* modules/x86/task/_thread_cpu_context.c