[cap-talk] Object Allocation

[Tom Bachmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To me, this appears to be largely a bootstrap problem. A program that
needs to create files gets passed a fileserver capability, etc. A
fileserver, like any user (-space) implemented object, is just a process.

So what "basic resources" are there that would need "static
constructors"? Processes, address spaces, memory and capability pages
come to my mind, but the exact list is not important, I think.

I would basically create highly privileged kernel implemented objects
for creating processes etc and provide them on startup (for example they
could be passed in fixed capability locations or be hardwired in the
system image if you are persistent), for the userspace resource
management facility to wrap.

Resource management always roots at the place where the resource is
implemented. So yes, I think there should be "static constructors" for
the most primitive objects. These "static constructors" are probably
wrapped by the resource management subsystem and passed around just like
any more complicated constructor.

Somehow all this seems to be obvious. I wonder if I misunderstood your
question.
- --
- -ness-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGjkwpvD/ijq9JWhsRAkaxAJ9s2QCk1dG+nt1FmCxJE1HavhD/iQCfXbh5
X2E5nFLCjC+L3iZEkSitSI4=
=HnJ1
-----END PGP SIGNATURE-----