[Top][All Lists]

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

Re: libpager deadlock

From: Samuel Thibault
Subject: Re: libpager deadlock
Date: Thu, 8 Apr 2010 16:15:00 +0200
User-agent: Mutt/1.5.12-2006-07-14

Sergio Lopez, le Thu 08 Apr 2010 16:07:20 +0200, a écrit :
> Anyway, let's suppose that m_o_lock_request only returns when the
> process has been completed. Then, why do we need an interface to nofity
> its completion (m_o_lock_completed)?

It seems I forgot to mention again that I really have a poor knowledge
of MIG interface etc. so I'm just trying to understand what's supposed
to happen, to know where to dig.

Sergio Lopez, le Thu 08 Apr 2010 16:07:20 +0200, a écrit :
> In memory_object.defs, m_o_lock_request is defined as simpleroutine, so
> a call to mach_msg_trap should only enqueue the message and return
> immediately.

Is this kind of information documented somewhere?  I can't find such
documentation in MIG's source.

> I don't have the stubs generated by MIG here, but the
> argument "option" should only have the MACH_SEND_MSG flag

mig_external kern_return_t __memory_object_lock_request
        return __mach_msg(&InP->Head, MACH_SEND_MSG|MACH_MSG_OPTION_NONE, 72, 


reply via email to

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