Dr. Phani Kishore Gadepalli

The option I'm thinking of: Consolidating kernel objects into one but still having three different capabilities. We'd have: ``` struct need_a_name { /* like the cos_defkernel_api's struct cos_aep_info */ struct...

Is `TLS` the main problem with many different runtimes, libraries that we foresee to support? I think we need to talk in a meeting to get broader context and be...

@gparmer Wednesday sounds good to me!

The problem is with the Kernel API for Retyping User/Kernel typed memory to Untyped COS Frame: `CAPTBL_OP_MEM_RETYPE2FRAME`. https://github.com/gparmer/Composite/blob/ppos/src/kernel/capinv.c#L1235-L1246 The purpose of this API as I understand is to Retype KMEM(kernel...

You're right and I think we have this problem with `components\Makefile.comp` also. We need to make them or at least rip out case specifics to include rules in their own...

As I read this, my initial thought was, this is worthless to do at user-level as we'd have more inter-leavings between kernel and user. That would essentially require complex logic...

Thank you for creating this issue and the information included is great! I've a few things to talk about, and I'm going to read this again and again and think...