ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-25 00:11:07 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
6d945e6a61
genode/repos/os/run/loader.run

72 lines
1.8 KiB
Plaintext
Raw Normal View History

Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
create_boot_directory
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
import_from_depot [depot_user]/src/[base_src] \
[depot_user]/pkg/[drivers_interactive_pkg] \
[depot_user]/src/init \
[depot_user]/src/nitpicker
build {
server/loader
test/loader
test/nitpicker
}
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
install_config {
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<config>
<parent-provides>
<service name="ROM"/>
<service name="IRQ"/>
<service name="IO_MEM"/>
<service name="IO_PORT"/>
<service name="PD"/>
<service name="RM"/>
<service name="CPU"/>
<service name="LOG"/>
</parent-provides>
<default-route>
<any-service> <parent/> <any-child/> </any-service>
Assign cap quotas in run scripts and recipes Issue #2398
2017-05-07 20:36:11 +00:00
</default-route>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
<default caps="100"/>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="timer">
<resource name="RAM" quantum="1M"/>
<provides><service name="Timer"/></provides>
</start>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
<start name="drivers" caps="1000">
<resource name="RAM" quantum="32M" constrain_phys="yes"/>
<binary name="init"/>
<route>
<service name="ROM" label="config"> <parent label="drivers.config"/> </service>
<service name="Timer"> <child name="timer"/> </service>
<any-service> <parent/> </any-service>
</route>
<provides>
<service name="Input"/> <service name="Framebuffer"/>
</provides>
</start>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="nitpicker">
<resource name="RAM" quantum="1M"/>
Rename "Nitpicker" service name to "Gui" Issue #3778
2020-06-11 14:06:21 +00:00
<provides> <service name="Gui"/> </provides>
Adapt run scripts to nitpicker config changes
2014-07-18 14:12:19 +00:00
<config>
Ajdust run scenarios for strict policy matching Issue #1901
2016-03-09 14:32:23 +00:00
<domain name="" layer="2" /> <default-policy domain=""/>
Adapt run scripts to nitpicker config changes
2014-07-18 14:12:19 +00:00
</config>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
</start>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="loader">
<resource name="RAM" quantum="1M"/>
<provides><service name="Loader"/></provides>
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
<config>
Make label prefixing more strict This patch unconditionally applies the labeling of sessions and thereby removes the most common use case of 'Child_policy::filter_session_args'. Furthermore, the patch removes an ambiguity of the session labels of sessions created by the parent of behalf of its child, e.g., the PD session created as part of 'Child' now has the label "<child-name>" whereas an unlabeled PD-session request originating from the child has the label "<child-name> -> ". This way, the routing-policy of 'Child_policy::resolve_session_request' can differentiate both cases. As a consequence, the stricter labeling must now be considered wherever a precise label was specified as a key for a session route or a server- side policy selection. The simplest way to adapt those cases is to use a 'label_prefix' instead of the 'label' attribute. Alternatively, the 'label' attribute may used by appending " -> " (note the whitespace). Fixes #2171
2016-11-24 14:28:32 +00:00
<policy label_prefix="test-loader">
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
<parent-rom name="testnit"/>
Build dynamically linked executables by default Fixes #2184
2016-12-01 18:00:11 +00:00
<parent-rom name="ld.lib.so"/>
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
</policy>
</config>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
</start>
Assign cap quotas in run scripts and recipes Issue #2398
2017-05-07 20:36:11 +00:00
<start name="test-loader" caps="200">
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<resource name="RAM" quantum="1G"/>
</start>
</config>}
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
build_boot_image { testnit loader test-loader }
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
run_genode_until forever
Reference in New Issue Copy Permalink