ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-19 05:37:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2cb635c3e3
genode/repos/base-foc/lib/mk/core-foc.inc

73 lines
2.8 KiB
PHP
Raw Normal View History

Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
GEN_CORE_DIR = $(BASE_DIR)/src/core
Generalize ABI mechanism to shared objects This patch make the ABI mechanism available to shared libraries other than Genode's dynamic linker. It thereby allows us to introduce intermediate ABIs at the granularity of shared libraries. This is useful for slow-moving ABIs such as the libc's interface but it will also become handy for the package management. To implement the feature, the build system had to be streamlined a bit. In particular, archive dependencies and shared-lib dependencies are now handled separately, and the global list of 'SHARED_LIBS' is no more. Now, the variable with the same name holds the per-target list of shared libraries used by the target.
2016-12-29 17:27:45 +00:00
LIBS += base-foc-common syscall-foc cxx
Merge base libraries into a single library This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18
2013-02-14 11:39:51 +00:00
base: hide internals of the Thread API This patch moves details about the stack allocation and organization the base-internal headers. Thereby, I replaced the notion of "thread contexts" by "stacks" as this term is much more intuitive. The fact that we place thread-specific information at the bottom of the stack is not worth introducing new terminology. Issue #1832
2016-01-23 13:42:55 +00:00
SRC_CC += stack_area.cc \
base: make stack area base specifiable for core When running core as the kernel inside every component, a separate stack area for core is needed that is different from the user-land component's one. Ref #2091
2017-06-20 13:01:05 +00:00
stack_area_addr.cc \
base-*: rename core_log.cc to core_log_out.cc Issue #2207
2017-12-12 09:53:03 +00:00
core_log_out.cc \
Assign threads to PD at its creation time This patch replaces the former 'Pd_session::bind_thread' function by a PD-capability argument of the 'Cpu_session::create_thread' function, and removes the ancient thread-start protocol via 'Rm_session::add_client' and 'Cpu_session::set_pager'. Threads are now bound to PDs at their creation time and implicitly paged according to the address space of the PD. Note the API change: This patch changes the signature of the 'Child' and 'Process' constructors. There is a new 'address_space' argument, which represents the region map representing the child's address space. It is supplied separately to the PD session capability (which principally can be invoked to obtain the PD's address space) to allow the population of the address space without relying on an 'Pd_session::address_space' RPC call. Furthermore, a new (optional) env_pd argument allows the explicit overriding of the PD capability handed out to the child as part of its environment. It can be used to intercept the interaction of the child with its PD session at core. This is used by Noux. Issue #1938
2016-04-20 19:12:57 +00:00
core_region_map.cc \
Integrate CAP session into PD session This patch integrates the functionality of the former CAP session into the PD session and unifies the approch of supplementing the generic PD session with kernel-specific functionality. The latter is achieved by the new 'Native_pd' interface. The kernel-specific interface can be obtained via the Pd_session::native_pd accessor function. The kernel-specific interfaces are named Nova_native_pd, Foc_native_pd, and Linux_native_pd. The latter change allowed for to deduplication of the pd_session_component code among the various base platforms. To retain API compatibility, we keep the 'Cap_session' and 'Cap_connection' around. But those classes have become mere wrappers around the PD session interface. Issue #1841
2016-01-19 19:24:22 +00:00
core_rpc_cap_alloc.cc \
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
cpu_session_component.cc \
base: separate native CPU from CPU session This patch unifies the CPU session interface across all platforms. The former differences are moved to respective "native-CPU" interfaces. NOVA is not covered by the patch and still relies on a custom version of the core-internal 'cpu_session_component.h'. However, this will soon be removed once the ongoing rework of pause/single-step on NOVA is completed. Fixes #1922
2016-03-30 13:34:37 +00:00
cpu_session_support.cc \
Separation of thread operations from CPU session This patch moves the thread operations from the 'Cpu_session' to the 'Cpu_thread' interface. A noteworthy semantic change is the meaning of the former 'exception_handler' function, which used to define both, the default exception handler or a thread-specific signal handler. Now, the 'Cpu_session::exception_sigh' function defines the CPU-session-wide default handler whereas the 'Cpu_thread::exception_sigh' function defines the thread-specific one. To retain the ability to create 'Child' objects without invoking a capability, the child's initial thread must be created outside the 'Child::Process'. It is now represented by the 'Child::Initial_thread', which is passed as argument to the 'Child' constructor. Fixes #1939
2016-05-10 16:05:38 +00:00
cpu_thread_component.cc \
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
dataspace_component.cc \
base: new interface for textual output Issue #1942
2016-05-03 14:31:17 +00:00
default_log.cc \
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
dump_alloc.cc \
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
io_mem_session_component.cc \
io_mem_session_support.cc \
base: remove pager code from public API Fix #1593
2015-06-19 12:58:18 +00:00
ipc_pager.cc \
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
irq_session_component.cc \
main.cc \
base: remove pager code from public API Fix #1593
2015-06-19 12:58:18 +00:00
pager.cc \
core: unify and simplify paging code (Fix #1641) For most platforms except of NOVA a distinction between pager entrypoint and pager activation is not needed, and only exists due to historical reasons. Moreover, the pager thread's execution path is almost identical between most platforms excluding NOVA, HW, and Fisco.OC. Therefore, this commit unifies the pager loop for the other platforms, and removes the pager activation class.
2015-07-29 08:58:17 +00:00
pager_object.cc \
core: add map method to pd_session interface The method can be used to trigger the eager insertion of page frames into page tables. Intention: to be used for memory used for DMA. Issue #2209
2017-08-02 15:30:49 +00:00
pd_session_support.cc \
base: separate native CPU from CPU session This patch unifies the CPU session interface across all platforms. The former differences are moved to respective "native-CPU" interfaces. NOVA is not covered by the patch and still relies on a custom version of the core-internal 'cpu_session_component.h'. However, this will soon be removed once the ongoing rework of pause/single-step on NOVA is completed. Fixes #1922
2016-03-30 13:34:37 +00:00
native_cpu_component.cc \
Integrate CAP session into PD session This patch integrates the functionality of the former CAP session into the PD session and unifies the approch of supplementing the generic PD session with kernel-specific functionality. The latter is achieved by the new 'Native_pd' interface. The kernel-specific interface can be obtained via the Pd_session::native_pd accessor function. The kernel-specific interfaces are named Nova_native_pd, Foc_native_pd, and Linux_native_pd. The latter change allowed for to deduplication of the pd_session_component code among the various base platforms. To retain API compatibility, we keep the 'Cap_session' and 'Cap_connection' around. But those classes have become mere wrappers around the PD session interface. Issue #1841
2016-01-19 19:24:22 +00:00
rpc_cap_factory.cc \
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
platform.cc \
core: generic ROM module initialization For most base platforms (except linux and sel4), the initialization of boot modules is the same. Thus, merge this default implementation in the new unit base/src/core/platform_rom_modules.cc. Ref #2490
2017-08-17 14:20:56 +00:00
platform_rom_modules.cc \
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
platform_pd.cc \
platform_services.cc \
platform_thread.cc \
Integrate core's RAM service into the PD service Fixes #2407
2017-05-11 18:03:28 +00:00
pd_session_component.cc \
core: split RAM dataspace factory from RAM service By separating the session-interface concerns from the mechanics of the dataspace creation, the code becomes simpler to follow, and the RAM session can be more easily merged with the PD session in a subsequent step. Issue #2407
2017-05-11 13:03:03 +00:00
ram_dataspace_support.cc \
ram_dataspace_factory.cc \
Consolidate RM service into PD session This patch integrates three region maps into each PD session to reduce the session overhead and to simplify the PD creation procedure. Please refer to the issue cited below for an elaborative discussion. Note the API change: With this patch, the semantics of core's RM service have changed. Now, the service is merely a tool for creating and destroying managed dataspaces, which are rarely needed. Regular components no longer need a RM session. For this reason, the corresponding argument for the 'Process' and 'Child' constructors has been removed. The former interface of the 'Rm_session' is not named 'Region_map'. As a minor refinement, the 'Fault_type' enum values are now part of the 'Region_map::State' struct. Issue #1938
2016-04-15 13:19:22 +00:00
region_map_component.cc \
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
rom_session_component.cc \
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
signal_source_component.cc \
base: restructure signal-submit initialization This patch allows core's 'Signal_transmitter' implementation to sidestep the 'Env::Pd' interface and thereby adhere to a stricter layering within core. The 'Signal_transmitter' now uses - on kernels that depend on it - a dedicated (and fairly freestanding) RPC proxy mechanism for signal deliver, instead of channeling signals through the 'Pd_session::submit' RPC function.
2017-05-10 18:11:38 +00:00
signal_transmitter_proxy.cc \
signal_receiver.cc \
Merge base libraries into a single library This patch simplifies the way of how Genode's base libraries are organized. Originally, the base API was implemented in the form of many small libraries such as 'thread', 'env', 'server', etc. Most of them used to consist of only a small number of files. Because those libraries are incorporated in any build, the checking of their inter-dependencies made the build process more verbose than desired. Also, the number of libraries and their roles (core only, non-core only, shared by both core and non-core) were not easy to capture. Hereby, the base libraries have been reduced to the following few libraries: - startup.mk contains the startup code for normal Genode processes. On some platform, core is able to use the library as well. - base-common.mk contains the parts of the base library that are identical by core and non-core processes. - base.mk contains the complete base API implementation for non-core processes Consequently, the 'LIBS' declaration in 'target.mk' files becomes simpler as well. In the most simple case, only the 'base' library must be mentioned. Fixes #18
2013-02-14 11:39:51 +00:00
thread_start.cc \
base: remove pager code from public API Fix #1593
2015-06-19 12:58:18 +00:00
trace_session_component.cc
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
INC_DIR += $(REP_DIR)/src/core/include \
Merge spin-lock implementations Separate spin-lock implementation from lock-implementation and put it into a non-public header, so it can be re-used by the DDE kit's and Fiasco.OC's capability-allocator spin lock. Fixes issue #123.
2012-02-29 14:23:06 +00:00
$(GEN_CORE_DIR)/include \
base: uniform base-internal header structure This patch establishes a common organization of header files internal to the base framework. The internal headers are located at '<repository>/src/include/base/internal/'. This structure has been choosen to make the nature of those headers immediately clear when included: #include <base/internal/lock_helper.h> Issue #1832
2016-01-20 17:27:18 +00:00
$(REP_DIR)/src/include \
$(BASE_DIR)/src/include
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
Provide Genode version information in log Fixes #551
2014-03-18 15:23:52 +00:00
include $(GEN_CORE_DIR)/version.inc
base: hide internals of the Thread API This patch moves details about the stack allocation and organization the base-internal headers. Thereby, I replaced the notion of "thread contexts" by "stacks" as this term is much more intuitive. The fact that we place thread-specific information at the bottom of the stack is not worth introducing new terminology. Issue #1832
2016-01-23 13:42:55 +00:00
vpath stack_area.cc $(GEN_CORE_DIR)
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
vpath cpu_session_component.cc $(GEN_CORE_DIR)
base: separate native CPU from CPU session This patch unifies the CPU session interface across all platforms. The former differences are moved to respective "native-CPU" interfaces. NOVA is not covered by the patch and still relies on a custom version of the core-internal 'cpu_session_component.h'. However, this will soon be removed once the ongoing rework of pause/single-step on NOVA is completed. Fixes #1922
2016-03-30 13:34:37 +00:00
vpath cpu_session_support.cc $(GEN_CORE_DIR)
Separation of thread operations from CPU session This patch moves the thread operations from the 'Cpu_session' to the 'Cpu_thread' interface. A noteworthy semantic change is the meaning of the former 'exception_handler' function, which used to define both, the default exception handler or a thread-specific signal handler. Now, the 'Cpu_session::exception_sigh' function defines the CPU-session-wide default handler whereas the 'Cpu_thread::exception_sigh' function defines the thread-specific one. To retain the ability to create 'Child' objects without invoking a capability, the child's initial thread must be created outside the 'Child::Process'. It is now represented by the 'Child::Initial_thread', which is passed as argument to the 'Child' constructor. Fixes #1939
2016-05-10 16:05:38 +00:00
vpath cpu_thread_component.cc $(GEN_CORE_DIR)
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
vpath dataspace_component.cc $(GEN_CORE_DIR)
vpath dump_alloc.cc $(GEN_CORE_DIR)
base: new interface for textual output Issue #1942
2016-05-03 14:31:17 +00:00
vpath default_log.cc $(GEN_CORE_DIR)
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
vpath io_mem_session_component.cc $(GEN_CORE_DIR)
vpath io_mem_session_support.cc $(GEN_CORE_DIR)
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
vpath main.cc $(GEN_CORE_DIR)
core: add map method to pd_session interface The method can be used to trigger the eager insertion of page frames into page tables. Intention: to be used for memory used for DMA. Issue #2209
2017-08-02 15:30:49 +00:00
vpath pd_session_support.cc $(GEN_CORE_DIR)
Integrate CAP session into PD session This patch integrates the functionality of the former CAP session into the PD session and unifies the approch of supplementing the generic PD session with kernel-specific functionality. The latter is achieved by the new 'Native_pd' interface. The kernel-specific interface can be obtained via the Pd_session::native_pd accessor function. The kernel-specific interfaces are named Nova_native_pd, Foc_native_pd, and Linux_native_pd. The latter change allowed for to deduplication of the pd_session_component code among the various base platforms. To retain API compatibility, we keep the 'Cap_session' and 'Cap_connection' around. But those classes have become mere wrappers around the PD session interface. Issue #1841
2016-01-19 19:24:22 +00:00
vpath pd_upgrade_ram_quota.cc $(GEN_CORE_DIR)
Integrate core's RAM service into the PD service Fixes #2407
2017-05-11 18:03:28 +00:00
vpath pd_session_component.cc $(GEN_CORE_DIR)
Consolidate RM service into PD session This patch integrates three region maps into each PD session to reduce the session overhead and to simplify the PD creation procedure. Please refer to the issue cited below for an elaborative discussion. Note the API change: With this patch, the semantics of core's RM service have changed. Now, the service is merely a tool for creating and destroying managed dataspaces, which are rarely needed. Regular components no longer need a RM session. For this reason, the corresponding argument for the 'Process' and 'Child' constructors has been removed. The former interface of the 'Rm_session' is not named 'Region_map'. As a minor refinement, the 'Fault_type' enum values are now part of the 'Region_map::State' struct. Issue #1938
2016-04-15 13:19:22 +00:00
vpath region_map_component.cc $(GEN_CORE_DIR)
Introduce platform-specific services for core By now all services in core where created, and registered in the generic main routine. Although there exists already a x86-specific service (I/O ports) there was no possibility to announce core-services for certain platforms only. This commit introduces a hook function in the 'Platform' class, that enables registration of platform-specific services. Moreover, the io-port service is offered on x86 platforms only now.
2012-10-02 11:11:58 +00:00
vpath rom_session_component.cc $(GEN_CORE_DIR)
core: TRACE service interface and implementation
2013-08-10 01:44:55 +00:00
vpath trace_session_component.cc $(GEN_CORE_DIR)
core: split RAM dataspace factory from RAM service By separating the session-interface concerns from the mechanics of the dataspace creation, the code becomes simpler to follow, and the RAM session can be more easily merged with the PD session in a subsequent step. Issue #2407
2017-05-11 13:03:03 +00:00
vpath ram_dataspace_factory.cc $(GEN_CORE_DIR)
base: restructure signal-submit initialization This patch allows core's 'Signal_transmitter' implementation to sidestep the 'Env::Pd' interface and thereby adhere to a stricter layering within core. The 'Signal_transmitter' now uses - on kernels that depend on it - a dedicated (and fairly freestanding) RPC proxy mechanism for signal deliver, instead of channeling signals through the 'Pd_session::submit' RPC function.
2017-05-10 18:11:38 +00:00
vpath signal_transmitter_proxy.cc $(GEN_CORE_DIR)
vpath signal_receiver.cc $(GEN_CORE_DIR)
Integrate CAP session into PD session This patch integrates the functionality of the former CAP session into the PD session and unifies the approch of supplementing the generic PD session with kernel-specific functionality. The latter is achieved by the new 'Native_pd' interface. The kernel-specific interface can be obtained via the Pd_session::native_pd accessor function. The kernel-specific interfaces are named Nova_native_pd, Foc_native_pd, and Linux_native_pd. The latter change allowed for to deduplication of the pd_session_component code among the various base platforms. To retain API compatibility, we keep the 'Cap_session' and 'Cap_connection' around. But those classes have become mere wrappers around the PD session interface. Issue #1841
2016-01-19 19:24:22 +00:00
vpath core_rpc_cap_alloc.cc $(GEN_CORE_DIR)
Assign threads to PD at its creation time This patch replaces the former 'Pd_session::bind_thread' function by a PD-capability argument of the 'Cpu_session::create_thread' function, and removes the ancient thread-start protocol via 'Rm_session::add_client' and 'Cpu_session::set_pager'. Threads are now bound to PDs at their creation time and implicitly paged according to the address space of the PD. Note the API change: This patch changes the signature of the 'Child' and 'Process' constructors. There is a new 'address_space' argument, which represents the region map representing the child's address space. It is supplied separately to the PD session capability (which principally can be invoked to obtain the PD's address space) to allow the population of the address space without relying on an 'Pd_session::address_space' RPC call. Furthermore, a new (optional) env_pd argument allows the explicit overriding of the PD capability handed out to the child as part of its environment. It can be used to intercept the interaction of the child with its PD session at core. This is used by Noux. Issue #1938
2016-04-20 19:12:57 +00:00
vpath core_region_map.cc $(GEN_CORE_DIR)
core: generic ROM module initialization For most base platforms (except linux and sel4), the initialization of boot modules is the same. Thus, merge this default implementation in the new unit base/src/core/platform_rom_modules.cc. Ref #2490
2017-08-17 14:20:56 +00:00
vpath platform_rom_modules.cc $(GEN_CORE_DIR)
Imported Genode release 11.11
2011-12-22 15:19:25 +00:00
vpath %.cc $(REP_DIR)/src/core
Clean up base-library structure This patch moves the base library from src/base to src/lib/base, flattens the library-internal directory structure, and moves the common parts of the library-description files to base/lib/mk/base.inc and base/lib/mk/base-common.inc. Furthermore, the patch fixes a few cosmetic issues (whitespace and comments only) that I encountered while browsing the result. Fixes #1952
2016-04-29 11:23:19 +00:00
vpath %.cc $(REP_DIR)/src/lib/base
Reference in New Issue Copy Permalink