2015-05-10 19:51:10 +02:00
|
|
|
/*
|
|
|
|
|
* \brief Instance of the core-local (Genode) capability space
|
|
|
|
|
* \author Norman Feske
|
|
|
|
|
* \date 2015-05-08
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* 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.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* base includes */
|
|
|
|
|
#include <base/native_types.h>
|
|
|
|
|
#include <base/printf.h>
|
|
|
|
|
|
|
|
|
|
/* base-internal includes */
|
|
|
|
|
#include <internal/capability_data.h>
|
|
|
|
|
#include <internal/capability_space_sel4.h>
|
|
|
|
|
|
|
|
|
|
/* core includes */
|
|
|
|
|
#include <core_capability_space.h>
|
|
|
|
|
#include <platform.h>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Core-specific supplement of the capability meta data
|
|
|
|
|
*/
|
|
|
|
|
class Genode::Native_capability::Data : public Capability_data
|
|
|
|
|
{
|
|
|
|
|
private:
|
|
|
|
|
|
2016-01-19 20:24:22 +01:00
|
|
|
Pd_session const *_pd_session = nullptr;
|
2015-05-10 19:51:10 +02:00
|
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
2016-01-19 20:24:22 +01:00
|
|
|
Data(Pd_session const *pd_session, Rpc_obj_key key)
|
2015-05-10 19:51:10 +02:00
|
|
|
:
|
2016-01-19 20:24:22 +01:00
|
|
|
Capability_data(key), _pd_session(pd_session)
|
2015-05-10 19:51:10 +02:00
|
|
|
{ }
|
|
|
|
|
|
|
|
|
|
Data() { }
|
|
|
|
|
|
2016-01-19 20:24:22 +01:00
|
|
|
bool belongs_to(Pd_session const *session) const
|
2015-05-10 19:51:10 +02:00
|
|
|
{
|
2016-01-19 20:24:22 +01:00
|
|
|
return _pd_session == session;
|
2015-05-10 19:51:10 +02:00
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
using namespace Genode;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Singleton instance of core-specific capability space
|
|
|
|
|
*/
|
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
|
|
struct Local_capability_space
|
|
|
|
|
:
|
2015-05-11 08:43:43 +02:00
|
|
|
Capability_space_sel4<1UL << Core_cspace::NUM_CORE_SEL_LOG2, 0UL,
|
2015-05-10 19:51:10 +02:00
|
|
|
Native_capability::Data>
|
|
|
|
|
{ };
|
|
|
|
|
|
|
|
|
|
static Local_capability_space &local_capability_space()
|
|
|
|
|
{
|
|
|
|
|
static Local_capability_space capability_space;
|
|
|
|
|
return capability_space;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/********************************************************************
|
|
|
|
|
** Implementation of the core-specific Capability_space interface **
|
|
|
|
|
********************************************************************/
|
|
|
|
|
|
|
|
|
|
Native_capability
|
|
|
|
|
Capability_space::create_rpc_obj_cap(Native_capability ep_cap,
|
2016-01-19 20:24:22 +01:00
|
|
|
Pd_session const *pd_session,
|
2015-05-10 19:51:10 +02:00
|
|
|
Rpc_obj_key rpc_obj_key)
|
|
|
|
|
{
|
|
|
|
|
/* allocate core-local selector for RPC object */
|
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 rpc_obj_sel = platform_specific()->core_sel_alloc().alloc();
|
2015-05-10 19:51:10 +02:00
|
|
|
|
|
|
|
|
/* create Genode capability */
|
|
|
|
|
Native_capability::Data &data =
|
2016-01-19 20:24:22 +01:00
|
|
|
local_capability_space().create_capability(rpc_obj_sel, pd_session,
|
2015-05-10 19:51:10 +02:00
|
|
|
rpc_obj_key);
|
|
|
|
|
|
|
|
|
|
ASSERT(ep_cap.valid());
|
|
|
|
|
|
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 ep_sel(local_capability_space().sel(*ep_cap.data()));
|
2015-05-10 19:51:10 +02:00
|
|
|
|
|
|
|
|
/* mint endpoint capability into RPC object capability */
|
|
|
|
|
{
|
|
|
|
|
seL4_CNode const service = seL4_CapInitThreadCNode;
|
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
|
|
|
seL4_Word const dest_index = rpc_obj_sel.value();
|
2015-05-10 19:51:10 +02:00
|
|
|
uint8_t const dest_depth = 32;
|
|
|
|
|
seL4_CNode const src_root = seL4_CapInitThreadCNode;
|
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
|
|
|
seL4_Word const src_index = ep_sel.value();
|
2015-05-10 19:51:10 +02:00
|
|
|
uint8_t const src_depth = 32;
|
|
|
|
|
seL4_CapRights const rights = seL4_AllRights;
|
|
|
|
|
seL4_CapData_t const badge = seL4_CapData_Badge_new(rpc_obj_key.value());
|
|
|
|
|
|
|
|
|
|
int const ret = seL4_CNode_Mint(service,
|
|
|
|
|
dest_index,
|
|
|
|
|
dest_depth,
|
|
|
|
|
src_root,
|
|
|
|
|
src_index,
|
|
|
|
|
src_depth,
|
|
|
|
|
rights,
|
|
|
|
|
badge);
|
|
|
|
|
ASSERT(ret == 0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return Native_capability(data);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/******************************************************
|
|
|
|
|
** Implementation of the Capability_space interface **
|
|
|
|
|
******************************************************/
|
|
|
|
|
|
|
|
|
|
Native_capability Capability_space::create_ep_cap(Thread_base &ep_thread)
|
|
|
|
|
{
|
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 ep_sel(ep_thread.tid().ep_sel);
|
2015-05-10 19:51:10 +02:00
|
|
|
|
2016-01-19 20:24:22 +01:00
|
|
|
/* entrypoint capabilities are not allocated from a PD session */
|
|
|
|
|
Pd_session const *pd_session = nullptr;
|
2015-05-10 19:51:10 +02:00
|
|
|
|
|
|
|
|
Native_capability::Data &data =
|
2016-01-19 20:24:22 +01:00
|
|
|
local_capability_space().create_capability(ep_sel, pd_session,
|
2015-05-10 19:51:10 +02:00
|
|
|
Rpc_obj_key());
|
|
|
|
|
|
|
|
|
|
return Native_capability(data);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
void Capability_space::dec_ref(Native_capability::Data &data)
|
|
|
|
|
{
|
|
|
|
|
local_capability_space().dec_ref(data);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
void Capability_space::inc_ref(Native_capability::Data &data)
|
|
|
|
|
{
|
|
|
|
|
local_capability_space().inc_ref(data);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Rpc_obj_key Capability_space::rpc_obj_key(Native_capability::Data const &data)
|
|
|
|
|
{
|
|
|
|
|
return local_capability_space().rpc_obj_key(data);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Capability_space::Ipc_cap_data Capability_space::ipc_cap_data(Native_capability const &cap)
|
|
|
|
|
{
|
|
|
|
|
return local_capability_space().ipc_cap_data(*cap.data());
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2015-05-11 08:43:43 +02:00
|
|
|
Native_capability Capability_space::lookup(Rpc_obj_key rpc_obj_key)
|
|
|
|
|
{
|
|
|
|
|
Native_capability::Data *data = local_capability_space().lookup(rpc_obj_key);
|
|
|
|
|
|
|
|
|
|
return data ? Native_capability(*data) : Native_capability();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2015-05-10 19:51:10 +02:00
|
|
|
unsigned Capability_space::alloc_rcv_sel()
|
|
|
|
|
{
|
|
|
|
|
return platform_specific()->alloc_core_rcv_sel();
|
|
|
|
|
}
|
2015-05-11 08:43:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
void Capability_space::reset_sel(unsigned sel)
|
|
|
|
|
{
|
|
|
|
|
return platform_specific()->reset_sel(sel);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Native_capability Capability_space::import(Ipc_cap_data ipc_cap_data)
|
|
|
|
|
{
|
2016-01-19 20:24:22 +01:00
|
|
|
/* imported capabilities are not associated with a PD session */
|
|
|
|
|
Pd_session const *pd_session = nullptr;
|
2015-05-11 08:43:43 +02:00
|
|
|
|
|
|
|
|
Native_capability::Data &data =
|
2016-01-19 20:24:22 +01:00
|
|
|
local_capability_space().create_capability(ipc_cap_data.sel, pd_session,
|
2015-05-11 08:43:43 +02:00
|
|
|
ipc_cap_data.rpc_obj_key);
|
|
|
|
|
|
|
|
|
|
return Native_capability(data);
|
|
|
|
|
}
|