genode/repos/os/run/thread_join.run

build "core init drivers/timer test/thread_join"

create_boot_directory

install_config {
	<config>
		<parent-provides>
			<service name="ROM"/>
			<service name="RAM"/>
			<service name="CPU"/>
			<service name="RM"/>
			<service name="PD"/>
			<service name="IRQ"/>
			<service name="IO_PORT"/>
			<service name="IO_MEM"/>
			<service name="LOG"/>
		</parent-provides>
		<default-route>
			<any-service> <parent/> <any-child/> </any-service>
		</default-route>
		<start name="timer">
			<resource name="RAM" quantum="1M"/>
			<provides><service name="Timer"/></provides>
		</start>
		<start name="test-thread_join">
			<resource name="RAM" quantum="10M"/>
		</start>
	</config>
}

build_boot_image "core ld.lib.so init timer test-thread_join"

append qemu_args "-nographic -m 64"

run_genode_until {.*--- Thread join test finished ---.*\n} 10
Add 'Thread_base::join()' Using the new 'join()' function, the caller can explicitly block for the completion of the thread's 'entry()' function. The test case for this feature can be found at 'os/src/test/thread_join'. For hybrid Linux/Genode programs, the 'Thread_base::join()' does not map directly to 'pthread_join'. The latter function gets already called by the destructor of 'Thread_base'. According to the documentation, subsequent calls of 'pthread_join' for one thread may result in undefined behaviour. So we use a 'Genode::Lock' on this platform, which is in line with the other platforms. Related to #194, #501 2012-11-16 12:53:37 +00:00			`build "core init drivers/timer test/thread_join"`

			`create_boot_directory`

			`install_config {`
			`<config>`
			`<parent-provides>`
			`<service name="ROM"/>`
			`<service name="RAM"/>`
			`<service name="CPU"/>`
			`<service name="RM"/>`
			`<service name="PD"/>`
			`<service name="IRQ"/>`
			`<service name="IO_PORT"/>`
			`<service name="IO_MEM"/>`
			`<service name="LOG"/>`
			`</parent-provides>`
			`<default-route>`
			`<any-service> <parent/> <any-child/> </any-service>`
			`</default-route>`
			`<start name="timer">`
			`<resource name="RAM" quantum="1M"/>`
			`<provides><service name="Timer"/></provides>`
			`</start>`
			`<start name="test-thread_join">`
			`<resource name="RAM" quantum="10M"/>`
			`</start>`
			`</config>`
			`}`

Build dynamically linked executables by default Fixes #2184 2016-12-01 18:00:11 +00:00			`build_boot_image "core ld.lib.so init timer test-thread_join"`
Add 'Thread_base::join()' Using the new 'join()' function, the caller can explicitly block for the completion of the thread's 'entry()' function. The test case for this feature can be found at 'os/src/test/thread_join'. For hybrid Linux/Genode programs, the 'Thread_base::join()' does not map directly to 'pthread_join'. The latter function gets already called by the destructor of 'Thread_base'. According to the documentation, subsequent calls of 'pthread_join' for one thread may result in undefined behaviour. So we use a 'Genode::Lock' on this platform, which is in line with the other platforms. Related to #194, #501 2012-11-16 12:53:37 +00:00
			`append qemu_args "-nographic -m 64"`

os/test: transition to new base API For all tests * use Component::construct instead of main * use new connection constructors with env argument * use log instead of printf For some tests * replace signal receivers with signal handlers * replace global static variables with Main class members * remove unnecessary multithreading * model test steps as classes that are independent from each other and managed by Main as constructibles * use references instead of pointers and exceptions instead of error codes * use Attached_* helpers intead of doing attach/detach manually * use helpers like String, Id_space, Registry instead of arrays and lists * make the run script suitable for automated execution and conclusion Ref #1987 2017-01-17 11:58:00 +00:00			`run_genode_until {.--- Thread join test finished ---.\n} 10`