Various glibc tests need it.

The payload is likely to play games with the stack area (like mmap()ing guard
pages), so give it virtual memory to play with instead of physical memory.

Fixes crash with mode=release.

Exceptions are challenging on x64 because the ABI reserves 128 bytes below
%rsp for local variables; this will be overwritten by an exception or
interrupt.  We can't use -mno-red-zone because the payload may not have been
compiled for it.  Instead, use the interrupt stack stack table mechanism
and a separate stack for exceptions.  May fix random corruptions when timers
are used.

Look up the build directory from the running object.

glibc headers define various standard functions as macros, which breaks
the build.  #undef them in the source files.

It is illegal to put a field after a variable-length array, what's its offset?
Breaks mode=release.

Silences 'Subproject commit -dirty' messages

Not completely silent unfortunately.

Benchmark suite

Example:

  make cmdline='java.so -jar bench.jar'

One test so far: java.lang.System.nanoTime()

We're only about 500% slower than native.

Note that the glue code to set up the class path is written in Java.

Needed by Java formatter.

Signed-off-by: Avi Kivity <avi@cloudius-systems.com>

This is inspired by the FreeBSD code, but nothing but the header and function
names are left of the original version.

Doesn't actually support real asynchronous execution as we're missing the concept
of waitqueues in osv as of now, but that will be added soon.

Created abstract base classes for device and drivers, changed the flow of driver loading / device probing

osv thread gdb support

'osv info threads'
'osv thread apply all' (most useful with 'backtrace')

The thread list is used by the debugger to inspect running and stopped threads.

This allows using mutexes in the scheduler code (obviously not in any
scheduling path).

The threads' stacks are created on the stack, which means their state is
corrupted after the stacks are overwritten.  Delete them.

they seem to break running new tests after them.