mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-21 14:37:50 +00:00
Genode OS Framework
armcpluspluscppframeworkgenodegoahypervisorlinuxmicrokernelnovaobject-capabilitiesoperating-systemosdevriscvsculpt-ossel4virtualizationx86
ba348b73e2
When re-configuring the NIC router, determine for each domain if at least one interface stays with the domain. If a domain fullfills this and has a dynamic IP config (received via a DHCP client), keep the IP config. To achieve this, the following changes have been made to the existing NIC router code: * Split-up Interface::handle_config into three steps: 1) Determine for each interface if its domain can keep its IP config or or if it has to mark it invalid. This must be done before (re-)attaching any interface because during "attach" several decisions are made based on the validity of the IP config of corresponding the domain. (E.g. whether to participate in sending DHCP DISCOVERs {IP config invalid} or whether to participate in sending pending ARP REQUESTs {IP config valid} ). 2) Detach, attach, or re-attach each interface according to the configuration. This must be done before re-considering the temporary state objects of each interface because the latter might have effects on the interfaces of remote domains which must then be in place already. 3) Re-consider temporary state objects of each interface. (E.g. transport layer connection states) * Re-work IP-config setter in a way that it works as follows: 1) If the old IP config is valid, let all local interfaces as well as remote interfaces that depend on the IP config of the domain detach from the old IP config. 2) Overwrite with new IP config 3) If the new IP config is valid, let all local interfaces as well as remote interfaces that depend on the IP config of the domain attach to the new IP config. Issue #2815 |
||
---|---|---|
depot | ||
doc | ||
repos | ||
tool | ||
.gitignore | ||
LICENSE | ||
README | ||
VERSION |
================================= Genode Operating System Framework ================================= This is the source tree of the reference implementation of the Genode OS architecture. For a general overview about the architecture, please refer to the project's official website: :Official project website for the Genode OS Framework: [https://genode.org/documentation/general-overview] The current implementation can be compiled for 8 different kernels: Linux, L4ka::Pistachio, L4/Fiasco, OKL4, NOVA, Fiasco.OC, seL4, and a custom kernel for running Genode directly on ARM-based hardware. Whereas the Linux version serves us as development vehicle and enables us to rapidly develop the generic parts of the system, the actual target platforms of the framework are microkernels. There is no "perfect" microkernel - and neither should there be one. If a microkernel pretended to be fit for all use cases, it wouldn't be "micro". Hence, all microkernels differ in terms of their respective features, complexity, and supported hardware architectures. Genode allows the use of each of the kernels listed above with a rich set of device drivers, protocol stacks, libraries, and applications in a uniform way. For developers, the framework provides an easy way to target multiple different kernels instead of tying the development to a particular kernel technology. For kernel developers, Genode contributes advanced workloads, stress-testing their kernel, and enabling a variety of application use cases that would not be possible otherwise. For users and system integrators, it enables the choice of the kernel that fits best with the requirements at hand for the particular usage scenario. Documentation ############# The primary documentation is the book "Genode Foundations", which is available on the front page of Genode website: :Download the book "Genode Foundations": [https://genode.org] The book describes Genode in a holistic and comprehensive way. It equips you with a thorough understanding of the architecture, assists developers with the explanation of the development environment and system configuration, and provides a look under the hood of the framework. Furthermore, it contains the specification of the framework's programming interface. The project has a quarterly release cycle. Each version is accompanied with detailed release documentation, which is available at the documentation section of the project website: :Release documentation: [https://genode.org/documentation/release-notes/] Directory overview ################## The source tree is composed of the following subdirectories: :'doc': This directory contains general documentation. Please consider the following document for a quick guide to get started with the framework: ! doc/getting_started.txt If you are curious about the ready-to-use components that come with the framework, please review the components overview: ! doc/components.txt :'repos': This directory contains the so-called source-code repositories of Genode. Please refer to the README file in the 'repos' directory to learn more about the roles of the individual repositories. :'tool': Source-code management tools and scripts. Please refer to the README file contained in the directory. :'depot' and 'public': Local depot and public archive of Genode packages. Please refer to ! doc/depot.txt for more details. Additional community-maintained components ########################################## The components found within the main source tree are complemented by a growing library of additional software, which can be seamlessly integrated into Genode system scenarios. :Genode-world repository: [https://github.com/genodelabs/genode-world] Contact ####### The best way to get in touch with Genode developers and users is the project's mailing list. Please feel welcome to join in! :Genode Mailing Lists: [https://genode.org/community/mailing-lists] Commercial support ################## The driving force behind the Genode OS Framework is the German company Genode Labs. The company offers commercial licensing, trainings, support, and contracted development work: :Genode Labs website: [https://www.genode-labs.com]