Cross Reference: /src/lib/librumpuser/rumpuser_pth

History log of /src/lib/librumpuser/rumpuser_pth_dummy.c
Revision	Date	Author	Comments
1.19	18-Aug-2025	andvar	s/flgas/flags/ in rumpuser_mutex_init() second argument name. No functional changes intended.
1.18	27-Dec-2017	ozaki-r	Distinguish spin mutex and adaptive mutex on rump kernels for LOCKDEBUG Formerly rump kernels treated the two types of mutexes as both adaptive for LOCKDEBUG for some reasons. Now we can detect violations of mutex restrictions on rump kernels such as taking an adaptive mutex with holding a spin mutex as well as normal kernels.
1.17	17-Jun-2014	alnsn	branches: 1.17.16; For consistency with other files in the same directory don't include <sys/cdefs.h> before __RCSID.
1.16	15-May-2013	pooka	branches: 1.16.4; Pass enums over the hypercall interface as ints to avoid some pathological scenarios from arising in setups where enums might be of a different size in the rump kernel and hypervisor.
1.15	07-May-2013	pooka	need the rw_downgrade/tryupgrade methods too
1.14	07-May-2013	pooka	update to recent interface changes
1.13	02-May-2013	pooka	Inform the rump kernel hypervisor of valid thread contexts so that the implementation can allocate and release storage for them in an optimal fashion, if necessary.
1.12	30-Apr-2013	pooka	make this build/work again
1.11	30-Apr-2013	pooka	In kthread_create(), pass the priority and cpu index down to the rump kernel hypervisor (though the current implementation doesn't take advantage of them).
1.10	27-Apr-2013	pooka	roll mutex init hypercalls into one (one of them already took a flag anyway)
1.9	27-Apr-2013	pooka	* integrate rumpuser_getversion() with the hypervisor initialization * rename some identifiers to better match reality
1.8	27-Apr-2013	pooka	Try to make sure that the appropriate calls to mutex_enter() takes a spin mutex (i.e. does not relinquish cpu context while trying to take the mutex). Bump the hypercall interface version number. I'll be doing a bunch of other cleanups to simplify the interface for the benefit of alternative hypervisor implementations. I'll be riding this bump and doing a second one only after I'm finished with all of the changes.
1.7	06-Nov-2012	pooka	Actually define the klock/unlock pointers. Not having the storage allocated for them created "interesting" effects with one compiler setup.
1.6	06-Nov-2012	pooka	one more routine
1.5	02-Nov-2012	pooka	implement mutex_owner()
1.4	02-Nov-2012	pooka	need rumpuser_mutex_init_kmutex() these days
1.3	02-Nov-2012	pooka	Start restoring the ability to run rump kernels on non-threading hypervisors. Step 1: make this compile again (it's not complete, but at least it compiles).
1.2	23-May-2011	joerg	branches: 1.2.4; 1.2.10; Ensure that rumpuser_thread_exit doesn't return.
1.1	26-Feb-2010	pooka	librumpuser is not _KERNEL code and does not belong in sys. Move the source files from src/sys/rump/librump/rumpuser to src/lib/librumpuser (from where it is already built). Even so, keep rumpuser.h in sys/rump/include for kernel source tree self-containment.
1.2.10.3	20-Aug-2014	tls	Rebase to HEAD as of a few days ago.
1.2.10.2	23-Jun-2013	tls	resync from head
1.2.10.1	20-Nov-2012	tls	Resync to 2012-11-19 00:00:00 UTC
1.2.4.2	22-May-2014	yamt	sync with head. for a reference, the tree before this commit was tagged as yamt-pagecache-tag8. this commit was splitted into small chunks to avoid a limitation of cvs. ("Protocol error: too many arguments")
1.2.4.1	16-Jan-2013	yamt	sync with (a bit old) head
1.16.4.1	10-Aug-2014	tls	Rebase.
1.17.16.1	13-Jan-2018	snj	Pull up following revision(s) (requested by ozaki-r in ticket #495): lib/librumpuser/rumpfiber.c: revision 1.13 lib/librumpuser/rumpuser_pth.c: revision 1.46 lib/librumpuser/rumpuser_pth_dummy.c: revision 1.18 sys/kern/kern_condvar.c: revision 1.40 sys/kern/kern_lock.c: revision 1.161 sys/kern/kern_mutex.c: revision 1.68 sys/kern/kern_rwlock.c: revision 1.48 sys/rump/include/rump/rumpuser.h: revision 1.115 sys/rump/librump/rumpkern/locks.c: revision 1.76-1.79 Apply C99-style struct initialization to lockops_t -- Tweak LOCKDEBUG macros (NFC) -- Distinguish spin mutex and adaptive mutex on rump kernels for LOCKDEBUG Formerly rump kernels treated the two types of mutexes as both adaptive for LOCKDEBUG for some reasons. Now we can detect violations of mutex restrictions on rump kernels such as taking an adaptive mutex with holding a spin mutex as well as normal kernels. -- rump: check if the mutex is surely owned by the caller in mutex_exit Unlocking a not-owned mutex wasn't detected well (it could detect if the mutex is not held by anyone but that's not enough). Let's check it (the check is the same as normal kernel's mutex). If LOCKDEBUG is enabled, give the check over LOCKDEBUG because it can provide better debugging information.

OpenGrok