NetBSD/tests
maxv bfb4017486 Rework the machine configuration interface.
Provide three ranges in the conf space: <libnvmm:0-100>, <MI:100-200> and
<MD:200-...>. Remove nvmm_callbacks_register(), and replace it by the conf
op NVMM_MACH_CONF_CALLBACKS, handled by libnvmm. The callbacks are now
per-machine, and the emulators should now do:

-	nvmm_callbacks_register(&cbs);
+	nvmm_machine_configure(&mach, NVMM_MACH_CONF_CALLBACKS, &cbs);

This provides more granularity, for example if the process runs two VMs
and wants different callbacks for each.
2019-05-11 07:31:56 +00:00
..
bin Fix an (apparent) ancient ash bug, that was apparently fixed sometime 2019-05-04 02:52:22 +00:00
crypto Timeout for evp test case is still not enough for qemu/sparc 2019-03-27 21:14:54 +00:00
dev Fix quoting (quotes really do not nest...) and remove a bunch of it 2019-04-10 06:13:21 +00:00
fs s/ are are / are / 2019-03-08 08:35:58 +00:00
games
include - add or adjust /* FALLTHROUGH */ where appropriate 2019-02-03 03:19:25 +00:00
ipf
kernel Fix typo 2019-04-25 19:37:09 +00:00
lib Rework the machine configuration interface. 2019-05-11 07:31:56 +00:00
libexec Avoid casting fun by switching ifunc helper functions to return 2018-03-09 20:15:03 +00:00
modules wether -> whether 2019-04-21 11:45:08 +00:00
net tests: dump kernel stats on cleanup 2019-04-18 07:56:54 +00:00
rump Fix a silly bug the "cancel thrash" test: the exit condition for the 2019-01-04 05:35:24 +00:00
sbin
share
sys Fixed issues with uvm_page_physunload_delete_end test case. 2019-01-16 13:54:17 +00:00
usr.bin Upgrade indent(1) 2019-04-04 15:27:35 +00:00
usr.sbin
h_macros.h
Makefile
Makefile.inc
README

$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $

When adding new tests, please try to follow the following conventions.

1. For library routines, including system calls, the directory structure of
   the tests should follow the directory structure of the real source tree.
   For instance, interfaces available via the C library should follow:

	src/lib/libc/gen -> src/tests/lib/libc/gen
	src/lib/libc/sys -> src/tests/lib/libc/sys
	...

2. Equivalently, all tests for userland utilities should try to follow their
   location in the source tree. If this can not be satisfied, the tests for
   a utility should be located under the directory to which the utility is
   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
   even though the source code for the program is located under src/external.

3. Otherwise use your own discretion.