drew/acadia
1
0
Fork 0
Code Issues 6 Pull requests Projects Releases Packages Wiki Activity Actions

[zion] Store capability ids on the CapabilityTable.

Browse source 
This is preferable to storing it in the capability itself since the id
is really just an index for the containing process.
This commit is contained in:
Drew Galbraith 2023-06-16 15:27:09 -07:00
parent b27672d5de
commit 75b1f2d21c
3 changed files with 21 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

12
zion/capability/capability_table.h
View file

@ -29,7 +29,11 @@ class CapabilityTable {
// FIXME: store this id here rather than in the capability.
uint64_t next_cap_id_ = 0x100;
// FIXME: use a map data structure.
LinkedList<RefPtr<Capability>> capabilities_;
struct CapEntry {
uint64_t id;
RefPtr<Capability> cap;
};
LinkedList<CapEntry> capabilities_;
};
template <typename T>
@ -37,7 +41,8 @@ uint64_t CapabilityTable::AddNewCapability(const RefPtr<T>& object,
uint64_t permissions) {
MutexHolder h(lock_);
uint64_t id = next_cap_id_++;
capabilities_.PushBack(MakeRefCounted<Capability>(object, id, permissions));
capabilities_.PushBack(
{.id = id, .cap = MakeRefCounted<Capability>(object, permissions)});
return id;
}
@ -45,5 +50,6 @@ template <typename T>
void CapabilityTable::AddNewCapabilityWithId(uint64_t id,
const RefPtr<T>& object,
uint64_t permissions) {
capabilities_.PushBack(MakeRefCounted<Capability>(object, id, permissions));
capabilities_.PushBack(
{.id = id, .cap = MakeRefCounted<Capability>(object, permissions)});
}