Get rid of static Atffiles and let bsd.test.mk generate them on the fly.

Add regression test to verify that linksets work correctly with rump.

branches: 1.1.2;
add regression test for module init/fini in rump

tests/rump/rumpkern: Use PROGDPLIBS, not explicit -L/-l.

This way we relink the t_* test programs whenever changes under
tests/rump/kernspace change libkernspace.a.

branches: 1.19.8;
Centralize the base rump libraries into a variable used by all the other
Makefiles so that we can make changes to it centrally as needed and have
less mess. Fixes the sun2 build that needs rumpvfs after librump after
the latest changes.

branches: 1.18.2;
Add -lrump after -lkernspace, because kernspace.a references symbols
from librump and hooray for static linking semantics.

Fixes sun2 build issue reported by kre@.

(XXX WTF did this only start failing after the addition of t_threadpool?)

Add rump-based test cases for threadpool(9).

branches: 1.16.2; 1.16.4;
Add simple test for workqueue(9)

branches: 1.15.16;
Fix static linking for the tests: -lrump is also used by -lrumpuser,
so we also need -lrump after -lrumpuser. Fixes build for sun2.

branches: 1.14.12; 1.14.22;
test remove signal delivery

elementary tests for rump sigmodels

Add some tests for lock errors. Notably, some of them fare nicely
with just the pthread consistency checks (which are enabled by
default in rumpuser), but others require real LOCKDEBUG.

Retire h_simpleserver and use rump_server instead.

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

Test copystr/copyinstr/copyoutstr focusing on the off-by-one cases.

As a notable caveat, this does not test the remote RPC paths of
those routines, which are arguably a little more complex.

tests for rump_lwproc

add tests for:
* threading
* tsleep variants
* uvm page busying and wanting

msdosfs depends on disk devices now

It seems that LDADD.file gets added to the linker invocation after
the LDADD variable expansion. To support static linking, ensure
that the common libraries gets tacked on at the end as well (order
matters for static linking), by using a convenience variable and
add it to the end of LDADD.t_modlinkset, as well as when doing the
general LDADD+= setting.

WARNS=4

Add regression test to verify that linksets work correctly with rump.

Apparently, there's not a clear dependency ordering for the libraries,
this becomes apparent when linking statically (e.g. as for sun2).
Add an extra instance of -lrump to the library list so that it can be
linked statically as well.

branches: 1.1.2;
add regression test for module init/fini in rump

bridge with the higher Makefile.inc

New testcase which checks that rump copyin/copyout/copyinstr/copyoutstr
version return EFAULT for special NULL "user" address.
ok pooka@.

branches: 1.1.6; 1.1.12;
Test copystr/copyinstr/copyoutstr focusing on the off-by-one cases.

As a notable caveat, this does not test the remote RPC paths of
those routines, which are arguably a little more complex.

lockme_DOUBLEINIT:
The failure message differs slightly when using LOCKDEBUG, modify the
expected pattern to cover both variants.

Fix detection of expected results. The rump kernel code apparently
includes source-code line numbers in the messages, so rather than
hard-coding them in the test, just use a reg-ex to match the text.

Fixes PR bin/52207

branches: 1.4.4;
Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.3.22;
Adjust MEMFREE expected output to recent kmem(9) changes.

branches: 1.2.6;
In case of LOCKDEBUG, expect certain text in the kernel output.

Add some tests for lock errors. Notably, some of them fare nicely
with just the pthread consistency checks (which are enabled by
default in rumpuser), but others require real LOCKDEBUG.

Hopefully fix some problems seen with MP support on non-x86, in particular
where curcpu() is defined as curlwp->l_cpu:

- mi_switch(): undo the ~2007ish optimisation to unlock curlwp before
calling cpu_switchto(). It's not safe to let other actors mess with the
LWP (in particular l->l_cpu) while it's still context switching. This
removes l->l_ctxswtch.

- Move the LP_RUNNING flag into l->l_flag and rename to LW_RUNNING since
it's now covered by the LWP's lock.

- Ditch lwp_exit_switchaway() and just call mi_switch() instead. Everything
is in cache anyway so it wasn't buying much by trying to avoid saving old
state. This means cpu_switchto() will never be called with prevlwp ==
NULL.

- Remove some KERNEL_LOCK handling which hasn't been needed for years.

branches: 1.9.14;
Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

more tests needing <sys/stat.h>

branches: 1.7.2;
call previous with the correct args too

check that setuid() works for procs with >1 lwp

+ rump_lwproc_newproc -> rump_lwproc_rfork()
+ add a tess for rump_lwproc_rfork()

implicit pid is 1 instead of 0 now

+tc (turns out the bug was elsewhere, but a test is always a test)

check that curlwp for an implicit context is NULL

tests for rump_lwproc

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.9.28;
hmm, using unifdef for the previous might have been a good idea ...

Now that atf gdb/coredump conflicts have been solved (thanks jmmv!),
remove USE_ATF ifdefs.

convert to ifdef USE_ATF

Disable module autoload so that it won't foil our module unload test.

Update to use newstyle rump_module interfaces.

WARNS=4

rump_module -> rump_pub_module

branches: 1.2.2;
don't hardcode /usr/lib path

add regression test for module init/fini in rump

fix various typos in comments, docs and log messages.

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.2.28;
WARNS=4

Add regression test to verify that linksets work correctly with rump.

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.2.26;
explicitly set the signal model

branches: 1.1.2;
elementary tests for rump sigmodels

tests/rump/rumpkern/t_sp: Go fishing for a rump_server core dump.

librumpuser: New RUMPUSER_DEBUG env var enables debug output.

Use it in t_sp:sigsafe to see if we can get more diagnostics out.

branches: 1.19.2;
Temporarily make PR t_sp:sigsafe noisier.

This is an attempt to diagnose why it's flaky in the releng testbeds
but not when I run it. This change will be backed out once we get
new testbed output.

rumpkern/t_sp: Save stdout and stderr to report on failure.

This is not very tidy at the moment, but it's an experiment using the
approach in PR bin/58112, to diagnose why t_sp:sigsafe keeps failing
intermittently. If this works, perhaps can tidy it up and apply it
to all the other tests that run rump_servers.

Format PR references consistently so that they can be automatically
turned into links in HTML reports.

Also skip the stress_short test - it just needs way too long to timeout
and fail.

Skip a few tests with reference to already existing PRs as after "recent"
scheduler changes these tests now leave rump_server processes around that
eat CPU and disturb later tests.

Get rid of all the -lrumpdev and -lrumpvfs that are no longer needed
after moving rump's mainbus from rumpdev to rumpkern.

Produces the same atf-run results as before.

branches: 1.13.14;

+ -lrumpdev

On systems that have only 32M of memory, the stress_short and
stress_long tests thrash a lot, and the stress_long test sometimes
times out, so skip them if we don't have at least 64M.

in reconnect, ignore any all reconnect messages

test for rumpclient reconnect feature

branches: 1.9.2;
test remove signal delivery

Execute a variety of syscalls in the stress test, including opening
files and sockets.

* run the killer stress test
* reduce default runtime to 5s

Make sure stressclient worker threads complete their operation
instead of hanging.

test rumpclient syscalls from a signal handler

Some tests for rumpclient fork.

Retire h_simpleserver and use rump_server instead.

use rump.halt in cleanup

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

branches: 1.2.2;
Add a test case that exercises repeated sceduling and cancelling of a job,
with periodic dropping of the interlock.

branches: 1.1.2;
Add rump-based test cases for threadpool(9).

Run both tests (rather than rumptest_threadjoin twice)

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.1.28;
add tests for:
* threading
* tsleep variants
* uvm page busying and wanting

Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.1.28;
add tests for:
* threading
* tsleep variants
* uvm page busying and wanting

tests/rump/rumpkern/t_vm: Re-enable test as xfail.

We do, after all, have a way to mark a test as expecting a crash,
namely, with atf_tc_expect_signal(SIGABRT, ...). Also cite the PR
while here.

It is unclear to me what the bug in the test is. Is it supposed to
get the page via uobj->uo_pager->pgo_get (perhaps in turn via
uvm_obj_wirepages) instead of uvm_pagealloc? This should be
explained more clearly in the message (or just fixed).

PR kern/55945: rump/rumpkern/t_vm:busypage fails since early December

branches: 1.7.2;

PR misc/57343 (Jim Spath) - fixed a typo in atf_tc_skip message.

for the busypage test, replace atf_tc_expect_fail() with atf_tc_skip()
because atf apparently has no way to expect a test program to crash.
fixes PR 55945.

the busypage test is buggy, expect it to fail.

branches: 1.4.16;
Don't play with "../.." in includes for h_macros.h; deal with it centrally.
Minor fixes.

branches: 1.3.14;
Starting with Rev. 1.191 of kern/subr_pool.c a pool has to be inactive
for at least 10 seconds before it can be reclaimed.

Change the uvmwait test timeout from 10 to 30 seconds so it has a chance
to reclaim memory and succeed.

branches: 1.2.6; 1.2.8;
add a vm allocator test which tests that:
* RUMP_MEMLIMIT works
* allocating memory with PR_NOWAIT will fail immediately if no memory
is available and PR_WAITOK will wait for memory to be available

add tests for:
* threading
* tsleep variants
* uvm page busying and wanting

workqueue(9): Avoid touching running work items in workqueue_wait.

As soon as the workqueue function has called, it is forbidden to
touch the struct work passed to it -- the function might free or
reuse the data structure it is embedded in.

So workqueue_wait is forbidden to search the queue for the batch of
running work items. Instead, use a generation number which is odd
while the thread is processing a batch of work and even when not.

There's still a small optimization available with the struct work
pointer to wait for: if we find the work item in one of the per-CPU
_pending_ queues, then after we wait for a batch of work to complete
on that CPU, we don't need to wait for work on any other CPUs.

PR kern/57574

XXX pullup-10
XXX pullup-9
XXX pullup-8

workqueue(9) tests: Add test for PR kern/57574.

XXX pullup-10
XXX pullup-9
XXX pullup-8

branches: 1.2.2; 1.2.8; 1.2.16;
Add a test case for workqueue_wait

Add simple test for workqueue(9)

test for rumpclient reconnect feature

branches: 1.4.2;
test rumpclient syscalls from a signal handler

Some tests for rumpclient fork.

h_reboot has been superceded by rump.halt

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

PR misc/54382: whenever open(2) is called with O_CREAT, make sure to
pass an open mode argument.

branches: 1.1.46;
Some tests for rumpclient fork.

h_reboot has been superceded by rump.halt

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

set reconnect property now that it's off by default

branches: 1.1.2;
test for rumpclient reconnect feature

Limit test duration based on wall time instead of loops
(took a long time on slow platforms).

branches: 1.2.2;
check that we actually go into the signal handler

test rumpclient syscalls from a signal handler

test remove signal delivery

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

fix fallout from including signal.h in rump_syscallargs.h

Execute a variety of syscalls in the stress test, including opening
files and sockets.

Give the stress queen two modes: one which nicely suggests an exit
and another one which keeps moet et chandon in her pretty cabinet.

Establish signal handler already in parent. Otherwise the child
might be killed before it has a chance to run.

Print some more info in an attempt to try to understand why the
test fails in automated test runs but not my desktop.

Make sure stressclient worker threads complete their operation
instead of hanging.

Don't use printf in a signal handler.

XXX: it would be nice if the deadlock with malloc were a little
more obvious, especially since gdb doesn't provide any clues unless
you compile libpthread with -g

check that child exits with an expected status

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

Centralize the base rump libraries into a variable used by all the other
Makefiles so that we can make changes to it centrally as needed and have
less mess. Fixes the sun2 build that needs rumpvfs after librump after
the latest changes.

Deal with fallout from the addition of
KERN_PROC_CWD in sysctl(3)
That is kern.proc.$$.KERN_PROC_CWD (I think - not that it matters here)

The effect is that -lrump now requires -lrumpvfs

This set of changes fixes (I believe) regular dynamic builds,
more might be required for static builds (will be verified soon).

branches: 1.5.16;
Move sysproxy support into a separate component, rumpkern_sysproxy,
instead of it being always provided by the rump kernel base. This
move accomplishes two things:

1) it is no longer necessary to provide sysproxy hypercall stubs for
platforms which do not want to use sysproxy
2) it is easier to reason about the security aspects, since configurations
not linking the sysproxy component simply do not support remote
system calls

discussed on rumpkernel-users

Fix static linking for the tests: -lrump is also used by -lrumpuser,
so we also need -lrump after -lrumpuser. Fixes build for sun2.

branches: 1.3.12; 1.3.22;
test remove signal delivery

Retire h_simpleserver and use rump_server instead.

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.

include <stdbool.h> for bool

test remove signal delivery

Retire h_simpleserver and use rump_server instead.

Add a simple and stress test cases for the rump remote syscall code.
Fun fact: since the server daemonizes into its own process group,
it's not in atf's pgrp. Use rump_sys_reboot() in atf cleanup to
kill the server after the test.