2015-05-01 20:03:08 +02:00
|
|
|
/*
|
|
|
|
* \brief Thread facility
|
|
|
|
* \author Norman Feske
|
|
|
|
* \date 2015-05-01
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Copyright (C) 2015 Genode Labs GmbH
|
|
|
|
*
|
|
|
|
* This file is part of the Genode OS framework, which is distributed
|
|
|
|
* under the terms of the GNU General Public License version 2.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Genode includes */
|
|
|
|
#include <base/printf.h>
|
|
|
|
#include <util/string.h>
|
|
|
|
|
|
|
|
/* core includes */
|
|
|
|
#include <platform_thread.h>
|
2015-05-12 12:48:03 +02:00
|
|
|
#include <platform_pd.h>
|
|
|
|
|
|
|
|
/* base-internal includes */
|
2016-01-20 18:27:18 +01:00
|
|
|
#include <base/internal/capability_space_sel4.h>
|
2015-05-01 20:03:08 +02:00
|
|
|
|
|
|
|
using namespace Genode;
|
|
|
|
|
|
|
|
|
2015-05-12 12:48:03 +02:00
|
|
|
/*****************************************************
|
|
|
|
** Implementation of the install_mapping interface **
|
|
|
|
*****************************************************/
|
|
|
|
|
|
|
|
class Platform_thread_registry : Noncopyable
|
|
|
|
{
|
|
|
|
private:
|
|
|
|
|
|
|
|
List<Platform_thread> _threads;
|
|
|
|
Lock _lock;
|
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
|
|
void insert(Platform_thread &thread)
|
|
|
|
{
|
|
|
|
Lock::Guard guard(_lock);
|
|
|
|
_threads.insert(&thread);
|
|
|
|
}
|
|
|
|
|
|
|
|
void remove(Platform_thread &thread)
|
|
|
|
{
|
|
|
|
Lock::Guard guard(_lock);
|
|
|
|
_threads.remove(&thread);
|
|
|
|
}
|
|
|
|
|
|
|
|
void install_mapping(Mapping const &mapping, unsigned long pager_object_badge)
|
|
|
|
{
|
|
|
|
Lock::Guard guard(_lock);
|
|
|
|
|
|
|
|
for (Platform_thread *t = _threads.first(); t; t = t->next()) {
|
|
|
|
if (t->pager_object_badge() == pager_object_badge)
|
|
|
|
t->install_mapping(mapping);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
Platform_thread_registry &platform_thread_registry()
|
|
|
|
{
|
|
|
|
static Platform_thread_registry inst;
|
|
|
|
return inst;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void Genode::install_mapping(Mapping const &mapping, unsigned long pager_object_badge)
|
|
|
|
{
|
|
|
|
platform_thread_registry().install_mapping(mapping, pager_object_badge);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2015-05-13 11:15:58 +02:00
|
|
|
/********************************************************
|
|
|
|
** Utilities to support the Platform_thread interface **
|
|
|
|
********************************************************/
|
|
|
|
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
static void prepopulate_ipc_buffer(addr_t ipc_buffer_phys, Cap_sel ep_sel)
|
2015-05-13 11:15:58 +02:00
|
|
|
{
|
|
|
|
/* IPC buffer is one page */
|
|
|
|
size_t const page_rounded_size = get_page_size();
|
|
|
|
|
|
|
|
/* allocate range in core's virtual address space */
|
|
|
|
void *virt_addr;
|
|
|
|
if (!platform()->region_alloc()->alloc(page_rounded_size, &virt_addr)) {
|
|
|
|
PERR("could not allocate virtual address range in core of size %zd\n",
|
|
|
|
page_rounded_size);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* map the IPC buffer to core-local virtual addresses */
|
|
|
|
map_local(ipc_buffer_phys, (addr_t)virt_addr, 1);
|
|
|
|
|
|
|
|
/* populate IPC buffer with thread information */
|
|
|
|
Native_utcb &utcb = *(Native_utcb *)virt_addr;
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
utcb.ep_sel = ep_sel.value();
|
2015-05-13 11:15:58 +02:00
|
|
|
|
|
|
|
/* unmap IPC buffer from core */
|
|
|
|
unmap_local((addr_t)virt_addr, 1);
|
|
|
|
|
|
|
|
/* free core's virtual address space */
|
|
|
|
platform()->region_alloc()->free(virt_addr, page_rounded_size);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2015-05-12 12:48:03 +02:00
|
|
|
/*******************************
|
|
|
|
** Platform_thread interface **
|
|
|
|
*******************************/
|
|
|
|
|
2015-05-01 20:03:08 +02:00
|
|
|
int Platform_thread::start(void *ip, void *sp, unsigned int cpu_no)
|
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
ASSERT(_pd);
|
|
|
|
ASSERT(_pager);
|
|
|
|
|
|
|
|
/* allocate fault handler selector in the PD's CSpace */
|
|
|
|
_fault_handler_sel = _pd->alloc_sel();
|
|
|
|
|
|
|
|
/* pager endpoint in core */
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
Cap_sel const pager_sel(Capability_space::ipc_cap_data(_pager->cap()).sel);
|
2015-05-12 12:48:03 +02:00
|
|
|
|
|
|
|
/* install page-fault handler endpoint selector to the PD's CSpace */
|
|
|
|
_pd->cspace_cnode().copy(platform_specific()->core_cnode(), pager_sel,
|
|
|
|
_fault_handler_sel);
|
|
|
|
|
2015-05-13 11:15:58 +02:00
|
|
|
/* allocate endpoint selector in the PD's CSpace */
|
|
|
|
_ep_sel = _pd->alloc_sel();
|
|
|
|
|
|
|
|
/* install the thread's endpoint selector to the PD's CSpace */
|
|
|
|
_pd->cspace_cnode().copy(platform_specific()->core_cnode(), _info.ep_sel,
|
|
|
|
_ep_sel);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Populate the thread's IPC buffer with initial information about the
|
|
|
|
* thread. Once started, the thread picks up this information in the
|
|
|
|
* 'Thread_base::_thread_bootstrap' method.
|
|
|
|
*/
|
|
|
|
prepopulate_ipc_buffer(_info.ipc_buffer_phys, _ep_sel);
|
2015-05-13 11:27:45 +02:00
|
|
|
|
2015-05-12 12:48:03 +02:00
|
|
|
/* bind thread to PD and CSpace */
|
|
|
|
seL4_CapData_t const guard_cap_data =
|
|
|
|
seL4_CapData_Guard_new(0, 32 - _pd->cspace_size_log2());
|
|
|
|
|
|
|
|
seL4_CapData_t const no_cap_data = { { 0 } };
|
|
|
|
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
int const ret = seL4_TCB_SetSpace(_info.tcb_sel.value(), _fault_handler_sel.value(),
|
|
|
|
_pd->cspace_cnode().sel().value(), guard_cap_data,
|
|
|
|
_pd->page_directory_sel().value(), no_cap_data);
|
2015-05-12 12:48:03 +02:00
|
|
|
ASSERT(ret == 0);
|
|
|
|
|
|
|
|
start_sel4_thread(_info.tcb_sel, (addr_t)ip, (addr_t)(sp));
|
2015-05-01 20:03:08 +02:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void Platform_thread::pause()
|
|
|
|
{
|
|
|
|
PDBG("not implemented");
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void Platform_thread::resume()
|
|
|
|
{
|
|
|
|
PDBG("not implemented");
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void Platform_thread::state(Thread_state s)
|
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
PDBG("not implemented");
|
2015-05-01 20:03:08 +02:00
|
|
|
throw Cpu_session::State_access_failed();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
Thread_state Platform_thread::state()
|
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
PDBG("not implemented");
|
2015-05-01 20:03:08 +02:00
|
|
|
throw Cpu_session::State_access_failed();
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
void Platform_thread::cancel_blocking()
|
|
|
|
{
|
|
|
|
PDBG("not implemented");
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
Weak_ptr<Address_space> Platform_thread::address_space()
|
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
ASSERT(_pd);
|
|
|
|
return _pd->weak_ptr();
|
2015-05-01 20:03:08 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2015-05-12 12:48:03 +02:00
|
|
|
void Platform_thread::install_mapping(Mapping const &mapping)
|
2015-05-01 20:03:08 +02:00
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
_pd->install_mapping(mapping);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
Platform_thread::Platform_thread(size_t, const char *name, unsigned priority,
|
|
|
|
addr_t utcb)
|
|
|
|
:
|
|
|
|
_name(name),
|
2015-05-13 11:15:58 +02:00
|
|
|
_utcb(utcb),
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
_pager_obj_sel(platform_specific()->core_sel_alloc().alloc())
|
2015-05-12 12:48:03 +02:00
|
|
|
|
|
|
|
{
|
2015-05-13 11:15:58 +02:00
|
|
|
_info.init(_utcb ? _utcb : INITIAL_IPC_BUFFER_VIRT);
|
2015-05-12 12:48:03 +02:00
|
|
|
platform_thread_registry().insert(*this);
|
2015-05-01 20:03:08 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
Platform_thread::~Platform_thread()
|
|
|
|
{
|
2015-05-12 12:48:03 +02:00
|
|
|
PDBG("not completely implemented");
|
|
|
|
|
|
|
|
platform_thread_registry().remove(*this);
|
sel4: update to version 2.1
This patch updates seL4 from the experimental branch of one year ago to
the master branch of version 2.1. The transition has the following
implications.
In contrast to the experimental branch, the master branch has no way to
manually define the allocation of kernel objects within untyped memory
ranges. Instead, the kernel maintains a built-in allocation policy. This
policy rules out the deallocation of once-used parts of untyped memory.
The only way to reuse memory is to revoke the entire untyped memory
range. Consequently, we cannot share a large untyped memory range for
kernel objects of different protection domains. In order to reuse memory
at a reasonably fine granularity, we need to split the initial untyped
memory ranges into small chunks that can be individually revoked. Those
chunks are called "untyped pages". An untyped page is a 4 KiB untyped
memory region.
The bootstrapping of core has to employ a two-stage allocation approach
now. For creating the initial kernel objects for core, which remain
static during the entire lifetime of the system, kernel objects are
created directly out of the initial untyped memory regions as reported
by the kernel. The so-called "initial untyped pool" keeps track of the
consumption of those untyped memory ranges by mimicking the kernel's
internal allocation policy. Kernel objects created this way can be of
any size. For example the phys CNode, which is used to store page-frame
capabilities is 16 MiB in size. Also, core's CSpace uses a relatively
large CNode.
After the initial setup phase, all remaining untyped memory is turned
into untyped pages. From this point on, new created kernel objects
cannot exceed 4 KiB in size because one kernel object cannot span
multiple untyped memory regions. The capability selectors for untyped
pages are organized similarly to those of page-frame capabilities. There
is a new 2nd-level CNode (UNTYPED_CORE_CNODE) that is dimensioned
according to the maximum amount of physical memory (1M entries, each
entry representing 4 KiB). The CNode is organized such that an index
into the CNode directly corresponds to the physical frame number of the
underlying memory. This way, we can easily determine a untyped page
selector for any physical addresses, i.e., for revoking the kernel
objects allocated at a specific physical page. The downside is the need
for another 16 MiB chunk of meta data. Also, we need to keep in mind
that this approach won't scale to 64-bit systems. We will eventually
need to replace the PHYS_CORE_CNODE and UNTYPED_CORE_CNODE by CNode
hierarchies to model a sparsely populated CNode.
The size constrain of kernel objects has the immediate implication that
the VM CSpaces of protection domains must be organized via several
levels of CNodes. I.e., as the top-level CNode of core has a size of
2^12, the remaining 20 PD-specific CSpace address bits are organized as
a 2nd-level 2^4 padding CNode, a 3rd-level 2^8 CNode, and several
4th-level 2^8 leaf CNodes. The latter contain the actual selectors for
the page tables and page-table entries of the respective PD.
As another slight difference from the experimental branch, the master
branch requires the explicit assignment of page directories to an ASID
pool.
Besides the adjustment to the new seL4 version, the patch introduces a
dedicated type for capability selectors. Previously, we just used to
represent them as unsigned integer values, which became increasingly
confusing. The new type 'Cap_sel' is a PD-local capability selector. The
type 'Cnode_index' is an index into a CNode (which is not generally not
the entire CSpace of the PD).
Fixes #1887
2016-02-03 14:50:44 +01:00
|
|
|
platform_specific()->core_sel_alloc().free(_pager_obj_sel);
|
2015-05-01 20:03:08 +02:00
|
|
|
}
|
2015-05-12 12:48:03 +02:00
|
|
|
|
|
|
|
|