14251 Commits

Author SHA1 Message Date
f1e85c0db8 version: 25.05 25.05 2025-05-28 08:23:47 +02:00
6a9d2bd1d5 depot: update recipe hashes 2025-05-28 08:23:47 +02:00
2e4d80b766 vmm_x86: enable kvm by default
Enable KVM by default, since beginning with Qemu 6.1.0 the initial
AMD-NPT fault is missing and no guest code is actually mapped by us ...

Qemu+KVM on AMD is working fine, however the initial guest fault address is
page aligned and not the exact IP as on Intel ...
2025-05-28 08:23:47 +02:00
d7f3933b8a test/cpu_sampler: increase expect timeout to 4s
On some platforms in rare cases the timeout of 2 seconds is not
enough. This can have different reasons: host-load when using qemu,
stucking serial line output, scheduling anomaly. But in general
the test succeeds when increasing the waiting time slightly.
2025-05-28 08:23:47 +02:00
61c844d1ee vbox6: port is x86_64 only 2025-05-28 08:23:46 +02:00
6bd2c8990a sel4: increase run script resources
Issue #5581
2025-05-28 08:23:46 +02:00
7b93dc5d88 driver/ahci: avoid using Xml_node::sub_node
Issue #5245
2025-05-28 08:23:46 +02:00
0b048de70c News item for version 25.05 2025-05-28 08:23:46 +02:00
a450eb054e Release notes for version 25.05 2025-05-28 08:23:46 +02:00
abf33c04ca base: remove Signal_receiver::unblock_signal_waiter
Additionally remove that code including the Kernel::cancel_next_await_signal
from base-hw.

Fix #5591
2025-05-28 08:23:46 +02:00
892610e5ef hw: remove Thread::_cancel_blocking and derivates
Replace Thread::_cancel_blocking call in Thread::_call_pending_signal
and remove all code that is not referenced anymore thereby.

Fix issue #5592
2025-05-28 08:23:46 +02:00
8deaabd667 sel4: release signal_source resources
on destruction

Issue #5581
2025-05-28 08:23:46 +02:00
7770d81555 sel4: remove Phys_alloc_failed exception
Issue #5581
2025-05-28 08:23:46 +02:00
1fdaddc8a5 doc/tool_chain.txt: version 25.05 2025-05-28 08:23:46 +02:00
124f0b12d7 heap: revert attachments before RAM presentation
On seL4 the kernel warns about invalid capabilities, since the attachments
are not valid anymore. Fixes run/vmm_x86 on seL4

Related to issue #5516
2025-05-28 08:23:46 +02:00
3482a661ed libc: move call_func implementation from header
When implemented as inline header function, __builtin_unreachable seems
to trigger dangerous compiler optimizations, like removing the '_state =
USER' because the compiler assumes a non-returning branch.

fixes #5587
2025-05-28 08:23:46 +02:00
f39336b402 Unify fixed-width C types
Fixes #5589
2025-05-28 08:23:46 +02:00
f741bac52a gpu/intel: Remove Mapping from Vram and tiling
The 'map' member of Vram was only used by set_tiling which is also not
used by current Mesa -> remove

issue #5245
2025-05-28 08:23:46 +02:00
d9fe20e9bf os: add 'for_each_return_address' for RISC-V
This enables 'Genode::backtrace' support for RISC-V

issue #5588
2025-05-28 08:23:46 +02:00
b074c67cae hw/riscv: make kernel compile
The 'memset' prototype got somehow lost.

issue #5588
2025-05-28 08:23:46 +02:00
01d239fd38 window_layouter: make maximized windows closable
Closing a window is reflected by a resize to 0x0. As the 'maximized' state
of a window prevented any resize, closing was impossible.

Fixes #5582
2025-05-28 08:23:46 +02:00
cb3349fd77 gdb: update to version 16.3
Issue #5540
2025-05-28 08:23:46 +02:00
3671cffb5d gdb_x86: replace chroot component
Fixes #5586
2025-05-28 08:23:46 +02:00
6ba1880789 dbg_download: replace chroot components
Fixes #5585
2025-05-28 08:23:46 +02:00
b722fe1ebc test-monitor_gdb: update memory map test patterns
Fixes #5584
2025-05-28 08:23:46 +02:00
1e1cecb30f download_debug_info: fix "used ->" route
Fixes #5583
2025-05-28 08:23:46 +02:00
2c997c97c5 vfs: prevent hiding of close() overloads
The change prevents the following build errors on riscv.

In file included from /data/depot/checker/api/vfs/2025-05-18/include/vfs/readonly_value_file_system.h:19,
                 from /data/depot/checker/src/vfs_legacy_oss/2025-05-18/src/lib/vfs/legacy_oss/vfs_oss.cc:22:
/data/depot/checker/api/vfs/2025-05-18/include/vfs/readonly_value_file_system.h: In instantiation of ‘class Vfs::Readonly_value_file_system<unsigned int>’:
/data/depot/checker/src/vfs_legacy_oss/2025-05-18/src/lib/vfs/legacy_oss/vfs_oss.cc:152:26:   required from here
  152 |                                 _channels_fs         .value(channels);
      |                                                      ^
/data/depot/checker/api/vfs/2025-05-18/include/vfs/single_file_system.h:229:22: error: ‘virtual void Vfs::Single_file_system::close(Vfs::Vfs_handle*)’ was hidden [-Werror=overloaded-virtual=]
  229 |                 void close(Vfs_handle *handle) override
      |                      ^~~~~
/data/depot/checker/api/vfs/2025-05-18/include/vfs/readonly_value_file_system.h:170:22: note:   by ‘void Vfs::Readonly_value_file_system< <template-parameter-1-1>, BUF_SIZE>::close(Vfs::Vfs_watch_handle*) [with T = unsigned int; unsigned int BUF_SIZE = 128]’
  170 |                 void close(Vfs_watch_handle *handle) override
      |                      ^~~~~

https://stackoverflow.com/questions/9995421/gcc-woverloaded-virtual-warnings
suggests to address this by an explicit using statement.

Issue #5540
2025-05-28 08:23:46 +02:00
d1505aed16 sel4: extend pd id allocator in core
to support max supported count of PDs and free PD ids on Platform_pd
destruction.

Issue #5581
2025-05-28 08:23:46 +02:00
0ff5ee2035 sel4: extend vm_space in core
from 16M physical memory at most per PD to 128M per PD (up to 1GB is possible).

Show the limitation also during bootup of core.

Issue #5581
2025-05-28 08:23:46 +02:00
1a78e71e1b tool/run/disk: use --apparent-size with du
otherwise the estimated size may be too small because of sparse files and
the creation of the image fails because of insufficient space in the image
file.

Seen with seL4 images

Issue #5581
2025-05-28 08:23:46 +02:00
c13b77b673 sel4: avoid assertion in ipc.cc
During run/bomb, an attempt to delegate an already revoked capability may
lead to:

Assertion failed: delegated
genode/repos/base-sel4/src/lib/base/ipc.cc:252

also in core and the system hangs up.

Instead, continue and return an invalid capability. The higher level session
code can, will and have to deal with invalid capabilities already.

Issue #5581
2025-05-28 08:23:46 +02:00
c63b8dfe30 sel4: handle Denied in page_table_registry
otherwise core faults with uncatched exception

Additionaly, make fatal errors in core platform visible.

Issue #5581
2025-05-28 08:23:45 +02:00
cc5b42ec03 sel4: release cap indices in components
Issue #5581
2025-05-28 08:23:45 +02:00
9a693ecf95 Add log-session to the black hole component
Fixes #5568
2025-05-28 08:23:45 +02:00
ef32f231ea nova: track successful creation of a thread
With this addition, we can avoid syscalls on invalid capabilities for EC and
SC utilization time if a thread construction failed.

Fixes #5569
2025-05-28 08:23:45 +02:00
ccab3a2067 driver/nvme: avoid using Xml_node::sub_node
Issue #5245.
2025-05-28 08:23:45 +02:00
329c76a1be driver/acpi: avoid using Xml_node::sub_node
Issue #5245
2025-05-28 08:23:45 +02:00
907ccc719a nitpicker: avoid using Xml_node::sub_node
Issue #5245
2025-05-28 08:23:45 +02:00
53e8a68c38 sequence: avoid exception during XML parsing
Issue #5245
2025-05-28 08:23:45 +02:00
4197e432e9 sandbox: avoid using Xml_node::sub_node
Issue #5245
2025-05-28 08:23:45 +02:00
1ae002469e base/quota_transfer.h: remove exceptions
This patch ultimately cleans base/child.cc from C++ exceptions.

Issue #5245
2025-05-28 08:23:45 +02:00
7107719d23 util/bit_allocator.h: remove C++ exceptions
This change affects the users of util/bit_array.h as well, e.g.,
os/packet_allocator.h, libc, and part_block.

Issue #5245
2025-05-28 08:23:45 +02:00
9567e1e7ad base/include: compatibility to -fno-exceptions
This commit introduces 'raise(Unexpected_error)' for situations
that were formerly reflected directly as exceptions. Those conditions
still result in an exception but with added diagnostics.

The few parts of the API that strictly rely on C++ exceptions
(Xml_node, GENODE_RPC_THROW) are now guarded via __EXCEPTIONS.

Issue #5245
2025-05-27 08:33:23 +02:00
805cbd539c base-linux: remove exceptions
Issue #5245
2025-05-27 08:33:23 +02:00
7fe575056d base: remove try/catch from expanding_parent
Since commit "base: remove diagnostic throws from base lib", client-side
IPC errors are no longer reflected as exceptions.

Issue #5245
2025-05-27 08:33:22 +02:00
d469235fe5 core: remove 'new' from stack-area allocator
Issue #5245
2025-05-27 08:33:22 +02:00
eecafa0459 core: remove 'new' from CPU service
Issue #5245
2025-05-27 08:33:22 +02:00
2bcaf6c51c core: remove 'new' from RAM-dataspace factory
Also drop the distinction between Alloc_ram_error and Alloc_error.

Issue #5245
2025-05-27 08:33:22 +02:00
e48976926a core: remove 'new' from TRACE service
Besides replacing 'new' by 'Memory::Constrained_obj_allocator',
this patch consolidates the error types of the RPC functions that
can produce allocation failures.

The patch also removes the use of 'Attached_ram_dataspace' and
'Attached_dataspace' because these utilities throw.

Allocation errors of the trace-control area are now explicitly reflected
by 'Constructed' state values to Cpu_root.

Issue #5245
2025-05-27 08:33:22 +02:00
c033d4fbfa core: remove 'new' from RM service
Besides replacing 'new' by Constrained_obj_allocator, the patch reuses
Alloc_error for Rm_session::Create_result.

Issue #5245
2025-05-27 08:33:22 +02:00