What happens to those master objects if the capabilities go poof?  Do they get locked up forever, or...as I suspect...do they just escheat to the public as abandoned?

On Thu, Nov 19, 2015 at 2:50 PM, Gerwin Klein <Gerwin.Klein@nicta.com.au> wrote:
Hi Robbie,

it depends on how your root thread is set up.

If it holds remaining master capabilities to objects in the system, you need to make sure those are not destroyed, because deleting them would delete those objects.

If you don’t want to hand out these master caps and untyped caps to the rest of the system (often there are good reasons for that), you would usually leave them in an inert CNode that also has a capability to itself. That CNode could just be the root thread CNode.

You can then safely destroy the root thread, e.g. make it suspend itself. If nobody else has a capability to it, it can never run again.


> On 20 Nov 2015, at 3:34 am, Robert VanVossen <Robert.VanVossen@dornerworks.com> wrote:
> Hello,
> I was wondering if I can safely destroy my application root thread after I have
> setup the capabilities and memory mappings for all of my other threads in the
> system?
> Thanks,
> Robbie VanVossen
> DornerWorks
> _______________________________________________
> Devel mailing list
> Devel@sel4.systems
> https://sel4.systems/lists/listinfo/devel


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
Devel mailing list