2011-12-22 16:19:25 +01:00
|
|
|
/*
|
|
|
|
* \brief Linux platform
|
|
|
|
* \author Christian Helmuth
|
|
|
|
* \author Norman Feske
|
|
|
|
* \date 2007-09-10
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
2017-02-20 13:23:52 +01:00
|
|
|
* Copyright (C) 2007-2017 Genode Labs GmbH
|
2011-12-22 16:19:25 +01:00
|
|
|
*
|
|
|
|
* This file is part of the Genode OS framework, which is distributed
|
2017-02-20 13:23:52 +01:00
|
|
|
* under the terms of the GNU Affero General Public License version 3.
|
2011-12-22 16:19:25 +01:00
|
|
|
*/
|
|
|
|
|
2016-01-20 20:52:51 +01:00
|
|
|
#ifndef _CORE__INCLUDE__PLATFORM_H_
|
|
|
|
#define _CORE__INCLUDE__PLATFORM_H_
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
#include <base/allocator_avl.h>
|
|
|
|
#include <base/lock_guard.h>
|
|
|
|
|
|
|
|
#include <platform_generic.h>
|
|
|
|
#include <platform_pd.h>
|
|
|
|
#include <platform_thread.h>
|
2015-09-17 14:16:59 +02:00
|
|
|
#include <synced_range_allocator.h>
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
#include <assertion.h>
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
namespace Genode {
|
|
|
|
|
|
|
|
using namespace Genode;
|
|
|
|
|
|
|
|
class Platform : public Platform_generic
|
|
|
|
{
|
|
|
|
private:
|
|
|
|
|
2012-12-04 16:51:24 +01:00
|
|
|
/**
|
|
|
|
* Allocator for core-internal meta data
|
|
|
|
*/
|
2015-09-17 14:16:59 +02:00
|
|
|
Synced_range_allocator<Allocator_avl> _core_mem_alloc;
|
2012-12-04 16:51:24 +01:00
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Rom_fs _dummy_rom_fs { };
|
|
|
|
|
|
|
|
struct Dummy_allocator : Range_allocator
|
|
|
|
{
|
|
|
|
void free(void *, size_t) override { ASSERT_NEVER_CALLED; }
|
|
|
|
bool need_size_for_free() const override { ASSERT_NEVER_CALLED; }
|
|
|
|
size_t consumed() const override { ASSERT_NEVER_CALLED; }
|
|
|
|
size_t overhead(size_t) const override { ASSERT_NEVER_CALLED; }
|
|
|
|
int add_range (addr_t, size_t ) override { ASSERT_NEVER_CALLED; }
|
|
|
|
int remove_range(addr_t, size_t ) override { ASSERT_NEVER_CALLED; }
|
|
|
|
void free(void *) override { ASSERT_NEVER_CALLED; }
|
|
|
|
size_t avail() const override { ASSERT_NEVER_CALLED; }
|
|
|
|
bool valid_addr(addr_t ) const override { ASSERT_NEVER_CALLED; }
|
|
|
|
bool alloc(size_t, void **) override { ASSERT_NEVER_CALLED; }
|
|
|
|
|
|
|
|
Alloc_return alloc_aligned(size_t, void **, int, addr_t, addr_t) override
|
|
|
|
{ ASSERT_NEVER_CALLED; }
|
|
|
|
|
|
|
|
Alloc_return alloc_addr(size_t, addr_t) override
|
|
|
|
{ ASSERT_NEVER_CALLED; }
|
|
|
|
|
|
|
|
} _dummy_alloc { };
|
|
|
|
|
2012-12-04 16:51:24 +01:00
|
|
|
/**
|
|
|
|
* Allocator for pseudo physical memory
|
|
|
|
*/
|
|
|
|
struct Pseudo_ram_allocator : Range_allocator
|
|
|
|
{
|
Follow practices suggested by "Effective C++"
The patch adjust the code of the base, base-<kernel>, and os repository.
To adapt existing components to fix violations of the best practices
suggested by "Effective C++" as reported by the -Weffc++ compiler
argument. The changes follow the patterns outlined below:
* A class with virtual functions can no longer publicly inherit base
classed without a vtable. The inherited object may either be moved
to a member variable, or inherited privately. The latter would be
used for classes that inherit 'List::Element' or 'Avl_node'. In order
to enable the 'List' and 'Avl_tree' to access the meta data, the
'List' must become a friend.
* Instead of adding a virtual destructor to abstract base classes,
we inherit the new 'Interface' class, which contains a virtual
destructor. This way, single-line abstract base classes can stay
as compact as they are now. The 'Interface' utility resides in
base/include/util/interface.h.
* With the new warnings enabled, all member variables must be explicitly
initialized. Basic types may be initialized with '='. All other types
are initialized with braces '{ ... }' or as class initializers. If
basic types and non-basic types appear in a row, it is nice to only
use the brace syntax (also for basic types) and align the braces.
* If a class contains pointers as members, it must now also provide a
copy constructor and assignment operator. In the most cases, one
would make them private, effectively disallowing the objects to be
copied. Unfortunately, this warning cannot be fixed be inheriting
our existing 'Noncopyable' class (the compiler fails to detect that
the inheriting class cannot be copied and still gives the error).
For now, we have to manually add declarations for both the copy
constructor and assignment operator as private class members. Those
declarations should be prepended with a comment like this:
/*
* Noncopyable
*/
Thread(Thread const &);
Thread &operator = (Thread const &);
In the future, we should revisit these places and try to replace
the pointers with references. In the presence of at least one
reference member, the compiler would no longer implicitly generate
a copy constructor. So we could remove the manual declaration.
Issue #465
2017-12-21 15:42:15 +01:00
|
|
|
bool alloc(size_t, void **out_addr)
|
2012-12-04 16:51:24 +01:00
|
|
|
{
|
|
|
|
*out_addr = 0;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2015-02-07 23:27:56 +01:00
|
|
|
Alloc_return alloc_aligned(size_t, void **out_addr, int,
|
|
|
|
addr_t, addr_t)
|
2012-12-04 16:51:24 +01:00
|
|
|
{
|
|
|
|
*out_addr = 0;
|
|
|
|
return Alloc_return::OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
Alloc_return alloc_addr(size_t, addr_t)
|
|
|
|
{
|
2015-02-12 11:26:18 +01:00
|
|
|
return Alloc_return::OK;
|
2012-12-04 16:51:24 +01:00
|
|
|
}
|
|
|
|
|
2015-04-14 14:14:20 +02:00
|
|
|
int add_range(addr_t, size_t) override { return 0; }
|
|
|
|
int remove_range(addr_t, size_t) override { return 0; }
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
void free(void *) override { }
|
|
|
|
void free(void *, size_t) override { }
|
|
|
|
size_t avail() const override { return ~0; }
|
|
|
|
bool valid_addr(addr_t) const override { return true; }
|
|
|
|
size_t overhead(size_t) const override { return 0; }
|
|
|
|
bool need_size_for_free() const override { return true; }
|
2012-12-04 16:51:24 +01:00
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
} _ram_alloc { };
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Constructor
|
|
|
|
*/
|
|
|
|
Platform();
|
|
|
|
|
|
|
|
|
|
|
|
/********************************
|
|
|
|
** Generic platform interface **
|
|
|
|
********************************/
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Range_allocator &core_mem_alloc() override { return _core_mem_alloc; }
|
|
|
|
Range_allocator &ram_alloc() override { return _ram_alloc; }
|
|
|
|
Range_allocator &io_mem_alloc() override { return _dummy_alloc; }
|
|
|
|
Range_allocator &io_port_alloc() override { return _dummy_alloc; }
|
|
|
|
Range_allocator &irq_alloc() override { return _dummy_alloc; }
|
|
|
|
Range_allocator ®ion_alloc() override { return _dummy_alloc; }
|
2017-05-07 22:44:15 +02:00
|
|
|
addr_t vm_start() const override { return 0; }
|
|
|
|
size_t vm_size() const override { return 0; }
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Rom_fs &rom_fs() override { return _dummy_rom_fs; }
|
2017-05-07 22:44:15 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
* On Linux, the maximum number of capabilities is primarily
|
|
|
|
* constrained by the limited number of file descriptors within
|
|
|
|
* core. Each dataspace and and each thread consumes one
|
|
|
|
* descriptor. However, all capabilies managed by the same
|
|
|
|
* entrypoint share the same file descriptor such that the fd
|
|
|
|
* limit would be an overly pessimistic upper bound.
|
|
|
|
*
|
|
|
|
* Hence, we define the limit somewhat arbitrary on Linux and
|
|
|
|
* accept that scenarios may break when reaching core's fd limit.
|
|
|
|
*/
|
|
|
|
size_t max_caps() const override { return 10000; }
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
void wait_for_exit();
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif /* _CORE__INCLUDE__PLATFORM_H_ */
|