[Top][All Lists]

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

Re: mach_port_t vs task_t (really ipc_space_t) in Mach header files

From: Marcus Brinkmann
Subject: Re: mach_port_t vs task_t (really ipc_space_t) in Mach header files
Date: Sun, 30 Sep 2001 04:48:47 +0200
User-agent: Mutt/1.3.22i

On Sat, Sep 29, 2001 at 09:56:05PM -0400, Roland McGrath wrote:
> There is probably some obscure reason having to do with mig stubs in the
> kernel why those ctype declarations are there.  At any rate, I'm
> disinclined to fiddle with the .defs files.

Ah, this is indeed true.  A simple test shows that this is not
straightforward at all.  For example, mig does automatically convert
mach_port_t into ipc_port_t for a KernelServer in some interfaces, and
something related to it (or even something else!) blew my naive attempt at
changing the ctype (and even my more sophisticated attempt involving
cservertype and cusertype)... might be that a lot of conditionals could
rectify this, but as I am not enthusiastic about changing those files either,
I guess I have to drop that idea.  (Although it is still interesting to know
more about this, and to understand why it is done that way).

I stipulate this was done for simplicity, rather than to imply that the
view of all users on all these ports should be mach_port_t (although the
original Mach docs all use mach_port_t everywhere).

The devil is in the details...

`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

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