4da52517c1
This patch removes the component_entry_point library, which used to proved a hook for the libc to intercept the call of the 'Component::construct' function. The mechansim has several shortcomings (see the discussion in the associated issue) and was complex. So we eventually discarded the approach in favor of the explicit handling of the startup. A regular Genode component provides a 'Component::construct' function, which is determined by the dynamic linker via a symbol lookup. For the time being, the dynamic linker falls back to looking up a 'main' function if no 'Component::construct' function could be found. The libc provides an implementation of 'Component::construct', which sets up the libc's task handling and finally call the function 'Libc::Component::construct' from the context of the appllication task. This function is expected to be provided by the libc-using application. Consequently, Genode components that use the libc have to implement the 'Libc::Component::construct' function. The new 'posix' library provides an implementation of 'Libc::Component::construct' that calls a main function. Hence, POSIX programs that merely use the POSIX API merely have to add 'posix' to the 'LIBS' declaration in their 'target.mk' file. Their execution starts at 'main'. Issue #2199 |
||
|---|---|---|
| .. | ||
| accloff | ||
| frontend | ||
| include | ||
| patches | ||
| spec | ||
| audiodrv.cpp | ||
| devices.cc | ||
| devxhci.cc | ||
| drivers.cc | ||
| dummies.cc | ||
| dynlib.cc | ||
| guest_memory.h | ||
| hm.cc | ||
| iommio.cc | ||
| ioport.cc | ||
| libc.cc | ||
| logger.cc | ||
| mm.cc | ||
| mm.h | ||
| network.cpp | ||
| pdm.cc | ||
| pgm.cc | ||
| README | ||
| rt.cc | ||
| sup.cc | ||
| sup.h | ||
| target.mk | ||
| thread.cc | ||
| unimpl.cc | ||
| util.h | ||
| vmm_memory.h | ||
| vmm_region.h | ||
VirtualBox configuration options ################################ XHCI controller =============== The virtual XHCI controller can be enabled with the following configuration option: <config xhci="yes"> IOAPIC ====== The virtual PCI model delivers IRQs to the PIC by default and to the IOAPIC only if the guest operating system selected the IOAPIC with the '_PIC' ACPI method and if it called the '_PRT' ACPI method afterwards. When running a guest operating system which uses the IOAPIC, but does not call these ACPI methods (for example Genode/NOVA), the configuration option <config force_ioapic="yes"> enforces the delivery of PCI IRQs to the IOAPIC.