hw: provide identification of a processor object

ref #1076
hw: multiprocessor aware processor scheduling

ref #1076
hw: consider affinity location in Platform_thread

ref #1076
hw: set affinity of core threads

ref #1076
hw: provide processor broadcasts in core

A processor broadcast executes a function on all available processors
which is needed at least to do MMU cache-flushes globally.

ref #1076
hw: apply MMU cache-flushes to all processors

ref #1076
affinity.run: allow testing with hw_arndale

ref #1076
mp_server.run: allow testing with hw_arndale

fix #1076
hw: Fix name of Page_flags type

The type was accidentally changed by "hw & arm_v6: clean up TLB driver"

ref #1076
scout: include scout/platform.h for new operator
Simplify Framebuffer::Session interface

This patch removes the 'Framebuffer::Session::release()' function from
the interface to make the mode-change protocol consistent with the way
the Rom_session interface handles ROM-module changes. That is, the
client acknowledges the release of its current dataspace by requesting a
new dataspace via the 'Framebuffer::Session::dataspace()' function.

Fixes #1057
libc: Don't filter out sigsetjmp from libc-gen

Issue #1085
tool: test result output of amtterm reset

"amtterm reset" returns 0 as exitcode even if the reset command failed.
So check explicitly the output of the command to detect the error case.
libc_fs: Make plugin thread safe

Issue #1090
rump: Add panic message
vbox: Increase quota for rump_fs in auto test
run: enable virtualbox auto test for nightly runs

With #1090 fixed the test should succeed now.
base: provide Thread_base::stack_size(size_t)

The new method enhances the stack of the targeted thread if it is smaller
than a given size.

ref #1075
noux: enhance stack of all noux programs

This is done because we ran into a stack overflow while compiling
Genodes core/main.cc with GCC in Noux.

fix #1075
hw: reset scheduling timeout implicitely

This is needed as soon as we do inter-processor interrupts to
inform a processor about a remote modification in its scheduling plan.
In this case we can not explicitely decide wether to reset timer
or not. Instead we must decide it according to the choices of the
scheduler before and after the modification.

ref #1088