mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-24 15:56:41 +00:00
be0a1742ac
This patch makes the trace-subject state as reflected to the trace monitor more accurate. Until now, a subject could be in UNTRACED or TRACED state. In reality, however, there exists an intermediate state after the trace monitor called 'trace' for the subject but before the subject locally activated the tracing (done when passing a trace point). This intermediate state was reflected as UNTRACED. Consequently, threads that never pass a trace point (e.g., just waiting for I/O) would remain to appear as UNTRACED even after enabling its tracing by the trace monitor. This is confusing. This patch replaces the former UNTRACED and TRACED states by three distinct states: UNATTACHED prior any call of 'trace' ATTACHED after a trace monitor called 'trace' but before the tracing is active TRACE tracing is active Fixes #4447 |
||
---|---|---|
.. | ||
board | ||
etc | ||
include | ||
lib | ||
mk | ||
ports | ||
recipes | ||
run | ||
src | ||
xsd | ||
README |
This is generic part of the Genode implementation. It consists of two parts: :_Core_: is the ultimate root of the Genode application tree and provides abstractions for the lowest-level hardware resources such as RAM, ROM, CPU, and generic device access. All generic parts of Core can be found here - for system-specific implementations refer to the appropriate 'base-<system>' directory. :_Base libraries and protocols_: that are used by each Genode component to interact with other components. This is the glue that holds everything together. _Core_ may export information about the hardware platform by an ROM called 'platform_info'. Depending on the platform, e.g. ARM or x86 or riscv, and depending on the boot mode and boot loader and kernel, some nodes may not be populated. !<platform_info> ! <acpi revision="2" rsdt="0x1fe93074" xsdt="0x1fe930e8"/> ! <boot> ! <framebuffer phys="0x7300000" width="1024" height="768" bpp="32"/> ! </boot> !</platform_info> If the ACPI RSDT and XSDT physical pointer is reported by the used kernel and/or bootloader, _Core_ may provide this information by the ROM. If the graphic device is initialised and can be directly used by a framebuffer driver, _Core_ may provide the physical pointer to the framebuffer, the resolution and color depth in bits.