ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-19 21:57:55 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
25f2c44874
genode/tool/run/boot_dir/fiasco

119 lines
3.2 KiB
Plaintext
Raw Normal View History

Genode application binary interface (ABI) This patch decouples the kernel-specific implementation of the dynamic linker from its kernel-agnostic binary interface. The name of the kernel-specific dynamic linker binary now corresponds to the kernel, e.g., 'ld-linux.lib.so' or 'ld-nova.lib.so'. Applications are no longer linked directly against a concrete instance of the dynamic linker but against a shallow stub called 'ld.lib.so'. This stub contains nothing but the symbols provided by the dynamic linker. It thereby represents the Genode ABI. At system-integration time, the kernel-specific run/boot_dir back ends integrate the matching the kernel-specific variant of the dynamic linker as 'ld.lib.so' into the boot image. The ABI symbol file for the dynamic linker is located at 'base/lib/symbols/ld'. It contains the joint ABI of all supported architectures. The new utility 'tool/abi_symbols' eases the creation of such an ABI symbol file for a given shared library. Its result should be manually inspected and edited as needed. The patch removes the 'syscall' library from 'base_libs.mk' to avoid polluting the kernel-agnostic ABI with kernel-specific interfaces. Issue #2190 Issue #2195
2016-12-09 22:09:17 +00:00
proc binary_name_ld_lib_so { } { return "ld-fiasco.lib.so" }
core: install core-<kernel>.o at bin/ By installing the core object to bin/, we follow the same convention as for regular binaries. This, in turn, enables us to ship core in a regular binary archive. The patch also adjusts the run tool to pick up the core object from bin/ for the final linking stage.
2017-04-05 08:18:35 +00:00
proc binary_name_core_o { } { return "core-fiasco.o" }
Disambiguate names of timer drivers Issue #2190
2016-12-10 22:22:13 +00:00
proc binary_name_timer { } { return "fiasco_timer_drv" }
Genode application binary interface (ABI) This patch decouples the kernel-specific implementation of the dynamic linker from its kernel-agnostic binary interface. The name of the kernel-specific dynamic linker binary now corresponds to the kernel, e.g., 'ld-linux.lib.so' or 'ld-nova.lib.so'. Applications are no longer linked directly against a concrete instance of the dynamic linker but against a shallow stub called 'ld.lib.so'. This stub contains nothing but the symbols provided by the dynamic linker. It thereby represents the Genode ABI. At system-integration time, the kernel-specific run/boot_dir back ends integrate the matching the kernel-specific variant of the dynamic linker as 'ld.lib.so' into the boot image. The ABI symbol file for the dynamic linker is located at 'base/lib/symbols/ld'. It contains the joint ABI of all supported architectures. The new utility 'tool/abi_symbols' eases the creation of such an ABI symbol file for a given shared library. Its result should be manually inspected and edited as needed. The patch removes the 'syscall' library from 'base_libs.mk' to avoid polluting the kernel-agnostic ABI with kernel-specific interfaces. Issue #2190 Issue #2195
2016-12-09 22:09:17 +00:00
foc,fiasco: symlink kernel files to bin/
2017-04-18 12:24:31 +00:00
proc kernel_files { } { return { fiasco sigma0-fiasco bootstrap-fiasco } }
Genode application binary interface (ABI) This patch decouples the kernel-specific implementation of the dynamic linker from its kernel-agnostic binary interface. The name of the kernel-specific dynamic linker binary now corresponds to the kernel, e.g., 'ld-linux.lib.so' or 'ld-nova.lib.so'. Applications are no longer linked directly against a concrete instance of the dynamic linker but against a shallow stub called 'ld.lib.so'. This stub contains nothing but the symbols provided by the dynamic linker. It thereby represents the Genode ABI. At system-integration time, the kernel-specific run/boot_dir back ends integrate the matching the kernel-specific variant of the dynamic linker as 'ld.lib.so' into the boot image. The ABI symbol file for the dynamic linker is located at 'base/lib/symbols/ld'. It contains the joint ABI of all supported architectures. The new utility 'tool/abi_symbols' eases the creation of such an ABI symbol file for a given shared library. Its result should be manually inspected and edited as needed. The patch removes the 'syscall' library from 'base_libs.mk' to avoid polluting the kernel-agnostic ABI with kernel-specific interfaces. Issue #2190 Issue #2195
2016-12-09 22:09:17 +00:00
Disambiguate kernel-specific file names This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190
2016-12-10 00:30:38 +00:00
proc fiasco_serial_esc_arg { } { return "-serial_esc " }
proc run_boot_string { } { return "\nL4 Bootstrapper" }
proc core_link_address { } { return "0x01000000" }
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
run: capture kernel msg to detect boot errors Handle boot errors like the old run tool did by checking a kernel specific string on boot up and start the run script timeout afterwards. Issue #1395.
2015-02-06 17:02:55 +00:00
run: modularize run tool
2015-01-08 21:08:48 +00:00
##
# Populate boot directory with binaries on fiasco
#
proc run_boot_dir {binaries} {
run: link all files in [run_dir]/genode to core This way, files copied from the depot are incorporated in addition to the files explicitly specified as boot modules. The patch also adds an automatic check for the validity of the XML syntax of boot modules ending with '.config'. Issue #2339
2017-04-03 13:39:36 +00:00
#
# Build kernel and dynamic linker on demand, if not yet present in
# '[run_dir]/genode/'
#
set kernel_arg ""
set ld_arg ""
if {![file exists [run_dir]/genode/fiasco]} { set kernel_arg "kernel/fiasco" }
if {![file exists [run_dir]/genode/ld.lib.so]} { set ld_arg "lib/ld/fiasco" }
set targets "$kernel_arg $ld_arg"
if {[llength $targets]} { build $targets }
if {$kernel_arg != ""} {
file copy -force [pwd]/bin/fiasco [run_dir]/genode/fiasco
file copy -force [pwd]/bin/sigma0-fiasco [run_dir]/genode/sigma0-fiasco
file copy -force [pwd]/bin/bootstrap-fiasco [run_dir]/genode/bootstrap-fiasco
}
Genode application binary interface (ABI) This patch decouples the kernel-specific implementation of the dynamic linker from its kernel-agnostic binary interface. The name of the kernel-specific dynamic linker binary now corresponds to the kernel, e.g., 'ld-linux.lib.so' or 'ld-nova.lib.so'. Applications are no longer linked directly against a concrete instance of the dynamic linker but against a shallow stub called 'ld.lib.so'. This stub contains nothing but the symbols provided by the dynamic linker. It thereby represents the Genode ABI. At system-integration time, the kernel-specific run/boot_dir back ends integrate the matching the kernel-specific variant of the dynamic linker as 'ld.lib.so' into the boot image. The ABI symbol file for the dynamic linker is located at 'base/lib/symbols/ld'. It contains the joint ABI of all supported architectures. The new utility 'tool/abi_symbols' eases the creation of such an ABI symbol file for a given shared library. Its result should be manually inspected and edited as needed. The patch removes the 'syscall' library from 'base_libs.mk' to avoid polluting the kernel-agnostic ABI with kernel-specific interfaces. Issue #2190 Issue #2195
2016-12-09 22:09:17 +00:00
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
build_core_image $binaries
run: link all files in [run_dir]/genode to core This way, files copied from the depot are incorporated in addition to the files explicitly specified as boot modules. The patch also adds an automatic check for the validity of the XML syntax of boot modules ending with '.config'. Issue #2339
2017-04-03 13:39:36 +00:00
#
# Move kernel files to distinct location within the boot directory so that
# we can remove [run_dir]/genode after the core image has been built.
#
file copy -force [run_dir]/genode/fiasco [run_dir]/kernel
file copy -force [run_dir]/genode/sigma0-fiasco [run_dir]/sigma0
file copy -force [run_dir]/genode/bootstrap-fiasco [run_dir]/bootstrap
exec rm -r [run_dir]/genode
run: modularize run tool
2015-01-08 21:08:48 +00:00
if {[have_include "image/iso"] || [have_include "image/disk"]} {
Disambiguate kernel-specific file names This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190
2016-12-10 00:30:38 +00:00
tool: use grub2 instead of grub1 for iso boot Fixes #2526
2017-09-20 20:56:00 +00:00
if {[have_include "image/disk"]} {
exec mkdir -p [run_dir]/boot/grub
exec cp [genode_dir]/tool/boot/bender [run_dir]/boot/bender
}
if {[have_include "image/iso"]} {
install_iso_bootloader_to_run_dir
}
run: modularize run tool
2015-01-08 21:08:48 +00:00
#
# Generate GRUB config file
#
# The core binary is part of the 'binaries' list but it must
# appear right after 'sigma0' as boot module. Hence the special case.
#
tool: use grub2 instead of grub1 for iso boot Fixes #2526
2017-09-20 20:56:00 +00:00
set fh [open "[run_dir]/boot/grub/grub.cfg" "WRONLY CREAT TRUNC"]
puts $fh "set timeout=0"
puts $fh "menuentry 'Genode on L4/Fiasco' {"
puts $fh " insmod multiboot"
puts $fh " multiboot /boot/bender"
foc,fiasco: symlink kernel files to bin/
2017-04-18 12:24:31 +00:00
puts $fh " module /bootstrap -serial"
puts $fh " module /kernel -serial -jdb_cmd=JH [fiasco_serial_esc_arg]"
puts $fh " module /sigma0"
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
puts $fh " module /image.elf"
tool: use grub2 instead of grub1 for iso boot Fixes #2526
2017-09-20 20:56:00 +00:00
puts $fh "}"
run: modularize run tool
2015-01-08 21:08:48 +00:00
close $fh
}
run_image
if {[have_include "load/tftp"]} {
#
# Install PXE bootloader pulsar
#
install_pxe_bootloader_to_run_dir
#
# Generate pulsar config file
#
set fh [open "[run_dir]/config-52-54-00-12-34-56" "WRONLY CREAT TRUNC"]
puts $fh " exec /boot/bender"
foc,fiasco: symlink kernel files to bin/
2017-04-18 12:24:31 +00:00
puts $fh " load /bootstrap -serial"
puts $fh " load /kernel -serial -serial_esc -jdb_cmd=JH"
puts $fh " load /sigma0"
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
puts $fh " load /image.elf"
run: modularize run tool
2015-01-08 21:08:48 +00:00
close $fh
generate_tftp_config
}
Add support for ipxe load (nova, foc, fiasco) This makes use of the iPXE sanboot command [1] which downloads and boots an ISO image directly via HTTP. Therefore, your RUN_OPT needs both --include image/iso and --include load/ipxe NOTE: The webserver serving the ISO image must support ranged requests, see [2]. [1] - http://ipxe.org/cmd/sanboot [2] - http://forum.ipxe.org/showthread.php?tid=7295&pid=10482#pid10482
2015-08-27 17:03:57 +00:00
if {[have_include "load/ipxe"]} {
create_ipxe_iso_config
update_ipxe_boot_dir
create_symlink_for_iso
}
run: modularize run tool
2015-01-08 21:08:48 +00:00
}
run: support for accessing depot content Run scripts can use the new 'import_from_depot' function to incorporate archive content from the depot into a scenario. The function must be called after the 'create_boot_directory' function and takes any number of pkg, src, or raw archives as arguments. An archive is specified as depot-relative path of the form <user>/<type>/name. Run scripts may call 'import_from_depot' repeatedly. An argument can refer to a specific version of an archive or just the version-less archive name. In the latter case, the current version (as defined by a corresponding archive recipe in the source tree) is used. If a 'src' archive is specified, the run tool integrates the content of the corrsponding binary archive into the scenario. The binary archives are selected according the spec values as defined for the build directory. As of now, only x86_32 and x86_64 are supported by the 'depot_spec' function. Issue #2339
2017-03-29 14:04:07 +00:00
##
# Base source archive within depot
#
run: non-fatal exit on unsupported base build config The kernel-specific boot dir scripts exit with 0 and log "Test requires..." to inform the logger frontend of the base-archive unavailability.
2018-04-16 11:33:20 +00:00
proc base_src { } {
run: support for accessing depot content Run scripts can use the new 'import_from_depot' function to incorporate archive content from the depot into a scenario. The function must be called after the 'create_boot_directory' function and takes any number of pkg, src, or raw archives as arguments. An archive is specified as depot-relative path of the form <user>/<type>/name. Run scripts may call 'import_from_depot' repeatedly. An argument can refer to a specific version of an archive or just the version-less archive name. In the latter case, the current version (as defined by a corresponding archive recipe in the source tree) is used. If a 'src' archive is specified, the run tool integrates the content of the corrsponding binary archive into the scenario. The binary archives are selected according the spec values as defined for the build directory. As of now, only x86_32 and x86_64 are supported by the 'depot_spec' function. Issue #2339
2017-03-29 14:04:07 +00:00
run: non-fatal exit on unsupported base build config The kernel-specific boot dir scripts exit with 0 and log "Test requires..." to inform the logger frontend of the base-archive unavailability.
2018-04-16 11:33:20 +00:00
if {[have_spec x86_32]} { return base-fiasco }
global specs
puts stderr "Test requires base-fiasco kernel archive, which is missing for this build configuration"
puts stderr " SPECS=\"$specs\""
exit 0
}
Reference in New Issue Copy Permalink