[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: physmem, simple containers

From: Marcus Brinkmann
Subject: Re: physmem, simple containers
Date: Tue, 27 Jan 2004 13:55:40 +0100
User-agent: Mutt/1.5.4i

On Tue, Jan 27, 2004 at 12:52:08PM +0100, Niels Möller wrote:
> But what about WORTEL_MSG_GET_CAP_REPLY? Despite its name, it is sent
> by physmem to wortel (like all the other wortel requests). It seems
> intended for having physmem give some capability to wortel. Exactly
> what is it that physmem should give wortel? (My guess was that it
> simply returns a container handle for the memory passed in the
> corresponding WORTEL_MSG_GET_CAP_REQUEST, but it seems I guessed
> wrong).

Yes, but it is the handle for the other task, like the task server.

You are looking at a simple "cap passing protocol" for the bootstrap case.
Wortel requests creation of caps on behalf of other tasks, and provides them
to these tasks.  Maybe this should merely be identical to the normal cap
passing protocol.


`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    address@hidden
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]