base: check cpu_session pointer during destruction

Issue #1122
run: limit created threads in test

The rm_session quota of the context area is not sufficient to start more
then ~95 threads per address space. If one really needs so many threads per
address space one could increase the quota or dynamically respond to it using
the Expanding_rm_session class. Until now there is no need to support so much
threads per address space.

Issue #1122
os: Add 'Framebuffer::Session::sync_sigh'

The new framebuffer-session function allows a client to register a
handler for receiving display-synchronization events.
os: Make buffer size of 'Reporter' configurable
os: Refine Attached_rom_dataspace::update
os: Add Rect::contains() to geometry utils
os: Add Point::operator ==
nitpicker: Consider menubar for pointer reports

The pointer-report facility used to report the screen-absolute position
of the mouse pointer. For nitpicker clients, however, this position is
meaningless because their coordinate is always constrained to the area
below the menu bar. This patch offsets the reported position
accordingly.
libc: don't take alien thread for main pthread

It covers bugs which we should detect and fix, especially depending on
the result of pthread_myself locking implementation (ours and vbox) takes
decision to take a lock or just to assume it is a reentrant locking attempt.

Fixes #1128
vbox: remove patches regarding ioport width check

Issue #1129
nova: mtd fields are unsigned

Bit 31 (FPU Mtd) got negative expanded when combined with 64bit value.

Detected during work on #1129
vmm: parameterize Vcpu_dispatcher

Pre-condition to realize #1129, to be able to let a vCPU handler thread also
be a pthread.
fixup "vmm: parameterize Vcpu_dispatcher"
vbox: join emt and vcpu handler thread

Fixes #1129
core: extend core memory allocator

* Allow to translate physical to virtual core addresses and vice versa
* Eliminate race introduced by commit "core: re-design memory allocator"

Ref #723
hw: restrict processor broadcast to TLB flushing

Removes the generic processor broadcast function call. By now, that call
was used for cross processor TLB maintance operations only. When core/kernel
gets its memory mapped on demand, and unmapped again, the previous cross
processor flush routine doesn't work anymore, because of a hen-egg problem.
The previous cross processor broadcast is realized using a thread constructed
by core running on top of each processor core. When constructing threads in
core, a dataspace for its thread context is constructed. Each constructed
RAM dataspace gets attached, zeroed out, and detached again. The detach
routine requires a TLB flush operation executed on each processor core.

Instead of executing a thread on each processor core, now a thread waiting
for a global TLB flush is removed from the scheduler queue, and gets attached
to a TLB flush queue of each processor. The processor local queue gets checked
whenever the kernel is entered. The last processor, which executed the TLB
flush, re-attaches the blocked thread to its scheduler queue again.

To ease uo the above described mechanism, a platform thread is now directly
associated with a platform pd object, instead of just associate it with the
kernel pd's id.

Ref #723
hw: map core on demand (fix #723)

Instead of mapping all physical memory 1:1 into core/kernel's address space,
this commit limits the 1:1 mapping to the binary image, and I/O memory
regions used by the kernel only. All subsequent memory accesses of core
are done by mapping the corresponding memory on demand, and not necessarily
1:1.

This commit has several side effects:

The page table code had to be revisited completely. The kernel inserts no
longer anything into the page tables, apart from the initial translations
to have the core/kernel image available when enabling the MMU. The page
tables and higher level translation tables are no longer named Tlb, but
Translation_table instead. There is no indirection class required to define
the translation tables of a concrete SoC, the appropriated ARM specifier
is sufficient.
The ability to map core's memory the same way like it's done for all other
protection domains, makes a special treatment of core's threads (no context
area) obsolete.

Ref #567 (partly solves it)
Fix #723
Fix #1068
hw: make core target require 'hw' spec (fix #599)
fixup "libc: don't take alien thread for main pthread"

/plain/krishna/src/genode/genode.git/libports/src/lib/pthread/thread.cc:463:48: required from here
/plain/krishna/src/genode/genode.git/base/include/util/misc_math.h:20:47: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
fixup "run: limit created threads in test"