This allows us to use threads early on.

We want to initialize the scheduler before the filesystem, so we can't
depend on elf::program.

This avoids using separate protocols for setup and runtime.

* 'master' of github.com:cloudius-systems/osv:
  build: fix javac indentation on quiet builds
  build: silence ant
  smp: bootstrap all processors to C code

several instances

It was trapped when I run qemu w/ additional virtio-blk device.
It seems that multiple drivers of the same instance aren't working well

afterwards issue a matching number of read request to verify the content.

While doing it fix an off by 1 of i

Still with minimal stack, no interrupt support, etc.

* 'master' of github.com:cloudius-systems/osv: (26 commits)
  acpi: integrate acpica
  mmu: export phys_cast
  mmu: implement phys_to_virt()
  Add acpica license
  external: add acpi component architecture (acpica) package
  fix the glibc-testsuite reference
  move filesystem related headers to include/
  Move Java support to java/
  Disband 'kern/'
  Move core source files to core/
  Move some headers to 'include/'
  Rename 'includes/' to 'include/'
  add sleep() from musl
  add statvfs/fstatvfs support
  add statfs/fstatfs support
  create /tmp during startup
  add the glibc block test
  run: use all available host cpu features for maximum performance
  mmap: trap attempts to remap physical memory
  pthread: allocate a vma for thread stack
  ...

requests and wait for the answers.

Now basic data exchange seems to work (w/o interrupts yet)

Simpler than phys_cast sometimes.

I've also added an osv/ prefix to make sure we don't clash with system headers.

We probably should either adopt this globally or drop it, but I fear we'll run into
problems with the latter approach.

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.