genode/repos/os/include/loader_session/client.h

66 lines
1.8 KiB
C
Raw Normal View History

2011-12-22 15:19:25 +00:00
/*
* \brief Client-side loader-session interface
* \author Christian Prochaska
* \date 2009-10-05
*/
/*
* Copyright (C) 2009-2017 Genode Labs GmbH
2011-12-22 15:19:25 +00:00
*
* This file is part of the Genode OS framework, which is distributed
* under the terms of the GNU Affero General Public License version 3.
2011-12-22 15:19:25 +00:00
*/
#ifndef _INCLUDE__LOADER_SESSION__CLIENT_H_
#define _INCLUDE__LOADER_SESSION__CLIENT_H_
#include <loader_session/loader_session.h>
#include <loader_session/capability.h>
#include <base/rpc_client.h>
2011-12-22 15:19:25 +00:00
namespace Loader { struct Session_client; }
2011-12-22 15:19:25 +00:00
struct Loader::Session_client : Genode::Rpc_client<Session>
{
explicit Session_client(Loader::Session_capability session)
: Rpc_client<Session>(session) { }
Dataspace_capability alloc_rom_module(Name const &name,
size_t size) override {
return call<Rpc_alloc_rom_module>(name, size); }
void commit_rom_module(Name const &name) override {
call<Rpc_commit_rom_module>(name); }
Capability quota accounting and trading This patch mirrors the accounting and trading scheme that Genode employs for physical memory to the accounting of capability allocations. Capability quotas must now be explicitly assigned to subsystems by specifying a 'caps=<amount>' attribute to init's start nodes. Analogously to RAM quotas, cap quotas can be traded between clients and servers as part of the session protocol. The capability budget of each component is maintained by the component's corresponding PD session at core. At the current stage, the accounting is applied to RPC capabilities, signal-context capabilities, and dataspace capabilities. Capabilities that are dynamically allocated via core's CPU and TRACE service are not yet covered. Also, the capabilities allocated by resource multiplexers outside of core (like nitpicker) must be accounted by the respective servers, which is not covered yet. If a component runs out of capabilities, core's PD service prints a warning to the log. To observe the consumption of capabilities per component in detail, the PD service is equipped with a diagnostic mode, which can be enabled via the 'diag' attribute in the target node of init's routing rules. E.g., the following route enables the diagnostic mode for the PD session of the "timer" component: <default-route> <service name="PD" unscoped_label="timer"> <parent diag="yes"/> </service> ... </default-route> For subsystems based on a sub-init instance, init can be configured to report the capability-quota information of its subsystems by adding the attribute 'child_caps="yes"' to init's '<report>' config node. Init's own capability quota can be reported by adding the attribute 'init_caps="yes"'. Fixes #2398
2017-05-08 19:35:43 +00:00
void cap_quota(Cap_quota limit) override {
call<Rpc_cap_quota>(limit); }
void ram_quota(Ram_quota quantum) override {
call<Rpc_ram_quota>(quantum); }
void constrain_geometry(Area size) override {
call<Rpc_constrain_geometry>(size); }
void parent_view(Gui::View_capability view) override {
call<Rpc_parent_view>(view); }
void view_ready_sigh(Signal_context_capability sigh) override {
call<Rpc_view_ready_sigh>(sigh); }
void fault_sigh(Signal_context_capability sigh) override {
call<Rpc_fault_sigh>(sigh); }
void start(Name const &binary, Name const &label = "") override {
call<Rpc_start>(binary, label); }
void view_geometry(Rect rect, Point offset) override {
call<Rpc_view_geometry>(rect, offset); }
Area view_size() const override {
return call<Rpc_view_size>(); }
};
2011-12-22 15:19:25 +00:00
#endif /* _INCLUDE__PLUGIN_SESSION__CLIENT_H_ */